0% found this document useful (0 votes)
6 views

5

Uploaded by

lllarohan08
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views

5

Uploaded by

lllarohan08
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

● Common Statements:

○ DATA: Declares variables.


○ SELECT: Retrieves data from database tables.
○ WRITE: Outputs data to the screen.
○ IF-ELSEIF-ENDIF: Conditional logic.
○ LOOP-ENDLOOP: Iterates over a set of data.
○ CASE-WHEN-ENDCASE: Selects different options based on a value.
○ MOVE: Assigns a value to a variable.
○ CLEAR: Resets a variable to its initial value.
● Example:
DATA: lv_matnr TYPE mara-matnr,
lv_maktx TYPE makt-maktx.

SELECT SINGLE matnr maktx


FROM mara
INTO (lv_matnr, lv_maktx)
WHERE matnr = '100-100'.

IF sy-subrc = 0.
WRITE: / 'Material:', lv_matnr, lv_maktx.
ELSE.
WRITE: / 'Material not found.'.
ENDIF.

1. User Exits and BAdIs: Understanding how enhancements are implemented in SAP.
● Enhancements: Modifications to the standard SAP system to meet specific business
requirements.
● User Exits:
○ Predefined points in SAP programs where you can add your own code.
○ Implemented as function module exits, screen exits, or menu exits.
○ T-code: SMOD (to find user exits), CMOD (to create projects and assign
enhancements)
● Business Add-Ins (BAdIs):
○ Object-oriented enhancements.
○ Provide more flexibility than user exits.
○ T-code: SE18 (BAdI Definition), SE19 (BAdI Implementation)
● Example:
○ You might use a user exit or BAdI to:
■ Add custom fields to a screen.
■ Perform additional validation checks.
■ Modify the behavior of a standard transaction.
■ Add custom logic to a program.
● Enhancement Framework:
○ Enhancement Spots are containers to group multiple BAdIs.
○ T-code: SE80
● Implicit Enhancements:
○ Code can be added to predefined places such as the beginning or end of a form
routine, function module, include, method of a global class.
XIII. Testing and Documentation
1. Testing Strategies:
● Unit Testing:
○ Testing individual units of code (e.g., function modules, programs, classes).
○ Performed by developers.
○ Example: Testing a custom function module that calculates a price.
● Integration Testing:
○ Testing the interaction between different modules or systems.
○ Performed by developers and functional consultants.
○ Example: Testing the integration between MM and FI for automatic account
determination.
● User Acceptance Testing (UAT):
○ Testing the system by end-users to ensure that it meets the business requirements.
○ Performed by business users.
○ Example: End-users testing the entire procure-to-pay process.
● Regression Testing:
○ Retesting previously tested functionality after changes have been made to the
system (e.g., after applying a support package or implementing a new
enhancement).
○ Ensures that new changes have not introduced any errors.
● Performance Testing:
○ Testing the performance of the system under load.
○ Ensures that the system can handle the expected volume of transactions.
● Cutover Testing:
○ Testing the cutover process from the old system to the new system.
1. Test Script Creation:
● Test Scripts: Detailed, step-by-step instructions for performing a test.
● Components of a Test Script:
○ Test Case ID
○ Test Case Description
○ Preconditions
○ Test Steps
○ Expected Results
○ Actual Results
○ Pass/Fail Status
○ Comments
● Example:
Test Case Test Case Preconditio Test Steps Expected Actual Pass/Fail Comments
ID Description ns Results Results
TC001 Create Material 1. Go to Purchase
Purchase and vendor transaction order is
Order master ME21N. 2. created
data exist Enter successfull
vendor, y.
material,
quantity,
and plant.
Test Case Test Case Preconditio Test Steps Expected Actual Pass/Fail Comments
ID Description ns Results Results
3. Save the
purchase
order.
1. Documentation
● User Manuals:
○ Provide step-by-step instructions for end-users on how to use the system.
○ Should be clear, concise, and easy to understand.
○ Should include screenshots and examples.
● Training Materials:
○ Used to train end-users on the system.
○ Can include presentations, exercises, and hands-on activities.
● Configuration Documentation:
○ Documents the configuration settings of the system.
○ Should include the rationale behind the configuration choices.
○ Important for troubleshooting and future changes.
● Functional Specifications:
○ Documents the requirements for enhancements or custom developments.
○ Should be detailed and unambiguous.
● Technical Specifications:
○ Documents the technical design of enhancements or custom developments.
○ Should include details about the code, tables, and data structures.
XIV. Authorization and Security
1. Basic concepts of Authorization Objects
● Authorization Objects:
○ Building blocks of the SAP authorization concept.
○ Define which fields can be used to restrict access to data and transactions.
○ Example: M_BEST_BSA (Document Type in Purchase Order)
○ T-code: SU21
● Authorization Fields:
○ The individual fields within an authorization object.
○ Example: For M_BEST_BSA, the fields might be ACTVT (Activity) and BSART
(Document Type).
● Authorization Values:
○ The specific values that are allowed for an authorization field.
○ Example: For the ACTVT field, the values might be 01 (Create), 02 (Change), 03
(Display).
1. Roles and Profiles
● Roles (T-code: PFCG):
○ Collections of authorizations that are assigned to users.
○ Define what a user is allowed to do in the system.
○ Example: A role called "Purchase Order Processor" might contain authorizations to
create, change, and display purchase orders.
○ Single Roles: Contain authorization for a specific task.
○ Composite Roles: Group multiple single roles.
● Profiles:
○ Generated from roles.
○ Contain the technical authorization data.
○ Note: In modern SAP systems, profiles are typically generated automatically from
roles, and direct profile maintenance is less common.
● User Master Record (T-code: SU01):
○ Contains the user ID, password, and assigned roles.
● Authorization Checks:
○ When a user executes a transaction, the system checks the user's authorizations to
determine if they are allowed to perform the action.
○ AUTHORITY-CHECK statement in ABAP code.
● Trace (T-code: STAUTHTRACE or ST01):
○ Used to trace authorization checks and identify missing authorizations.
● Important Authorization Objects for MM:
○ M_BEST_BSA: Document Type in Purchase Order
○ M_BEST_EKG: Purchasing Group in Purchase Order
○ M_BEST_EKO: Purchasing Organization in Purchase Order
○ M_BEST_WRK: Plant in Purchase Order
○ M_MATE_MAT: Material Master: Materials
○ M_MATE_MAN: Material Master: Material Types
○ M_MATE_WRK: Material Master: Plants
○ M_MSEG_BMB: Material Documents: Movement Type
○ M_MSEG_BWA: Goods Movements: Movement Type
○ M_MSEG_WWA: Goods Receipt: Plant
○ M_RECH_WRK: Invoice Verification: Plant
○ M_RECH_SPG: Invoice Verification: Blocking Reasons
XV. Further Learning and Certification
1. Overview of Advanced Topics in SAP S/4HANA Sourcing and Procurement
● Service Procurement:
○ Procuring services instead of materials.
○ Service master records, service entry sheets, and service acceptance.
○ Integration with Project System (PS) for project-based services.
● Batch Management and Serial Number Management (Detailed):
○ Managing materials in batches or with unique serial numbers.
○ Tracking characteristics, expiration dates, and other information.
○ Used in industries such as pharmaceuticals, food, and chemicals.
● Supplier Relationship Management (SRM):
○ A separate SAP solution for managing relationships with suppliers.
○ Includes functionalities for supplier qualification, sourcing, contract management,
and supplier collaboration.
● Ariba Integration:
○ SAP Ariba is a cloud-based procurement solution that can be integrated with SAP
S/4HANA.
○ Provides functionalities for sourcing, procurement, and supplier collaboration.
● Release Strategy with Classification:
○ Using characteristics and classes to define release strategies for purchasing
documents.
● Reporting with CDS Views:
○ Creating custom reports using Core Data Services (CDS) views.
● Workflow:
○ Automating business processes using SAP Workflow.
1. SAP Certification:
● C_TS452_XXXX - SAP Certified Application Associate - SAP S/4HANA Sourcing and
Procurement (where XXXX is the year of exam):
○ The main certification for SAP S/4HANA Sourcing and Procurement.
○ Covers the topics in this syllabus.
○ Requires a good understanding of the configuration and use of the system.
● Preparation:
○ Take SAP training courses (see below).
○ Study the SAP documentation.
○ Gain hands-on experience with the system.
○ Practice with sample questions.
● Other Relevant Certifications:
○ C_S4CS_XXXX - SAP Certified Application Associate - SAP S/4HANA Cloud
for Supply Chain
○ C_S4FTR_XXXX - SAP Certified Application Associate - Treasury with SAP
S/4HANA
○ C_S4CFI_XXXX - SAP Certified Application Associate - SAP S/4HANA Cloud
for Finance
1. Recommended Courses (Based on SAP Learning Hub):
● S4H00 - SAP S/4HANA Overview: Introduction to SAP S/4HANA.
● S4PR1 - SAP S/4HANA Sourcing and Procurement - Functionality and Innovations:
○ Covers the core functionalities of SAP S/4HANA Sourcing and Procurement.
○ Highlights the new features and innovations in S/4HANA.
● S4PR2 - SAP S/4HANA Sourcing and Procurement - Configuration and
Customizing:
○ Covers the configuration of SAP S/4HANA Sourcing and Procurement.
● TS450 - SAP S/4HANA Sourcing and Procurement - Academy Part 1:
○ First part of the academy course for Sourcing and Procurement.
● TS452 - SAP S/4HANA Sourcing and Procurement - Academy Part 2:
○ Second part of the academy course for Sourcing and Procurement.
● Consider exploring courses on Data Migration, Integration and ABAP for functional
consultants.
Note: This combined syllabus provides a robust framework for learning SAP MM in S/4HANA.
Remember that real-world experience through projects and continuous learning are key to
becoming a proficient SAP professional. The specific course names and codes may vary slightly
depending on the region and the latest updates from SAP. Always refer to the official SAP
Training and Certification website (training.sap.com) or the SAP Learning Hub for the most
up-to-date information.
Key Takeaways:
● Practice is Crucial: The best way to learn SAP is by doing. Get hands-on experience
with the system as much as possible.
● Focus on Understanding: Don't just memorize T-codes. Understand the underlying
concepts and processes.
● Integration is Key: SAP modules are highly integrated. Learn how MM interacts with
other modules.
● Stay Up-to-Date: SAP is constantly evolving. Keep up with the latest changes and
innovations.
● Utilize SAP Resources: SAP provides a wealth of resources, including documentation,
training courses, and online communities. Take advantage of these resources to enhance
your learning.
By following this detailed syllabus and dedicating yourself to continuous learning, you will be
well on your way to mastering SAP S/4HANA Sourcing and Procurement! Good luck!

You might also like