This Blog is mainly on SAP Exam Questions and Selected "How-to" SAP processes

Monday, November 27, 2023

Q&A in Class (2023-12-01) S4200

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Storage Location Control

In ECC for setting up a Storage Location to be ignore by MRP Planning, it is possible to setup in MRP4 data view at the Storage Location segment with an MRP Indicator "1", in this way the Storage Location will be segmented from the Stock Requirement List and not Planned. 



The above 3 slides are extracts of setup in ECC6 EhP8. 

BUT what about S/4 2022 where Storage Location data segment in Material Master MRP4 view is no longer available. 

Check the following link to the Blog Post for the Possible Solution:
SAP PP - Storage Location MRP (ECC EhP8 vs S/4 2022)


---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Limited Production Order creation for a Material

Requirement is to only allow certain Materials to be created using allowed Order Types. For example, a Material is not allowed to use "Rework" Order type but only allowed "Standard" Order type. When user try to create Production Order for the Material with "Rework" Order type should be blocked from processing the Order. 

There isn't any standard features that supports the above scenario.

Suggestion 1: Use the Production Scheduling Profile (which contains a default MTS/MTO Order Type) which can be assigned to the Material + Plant combination. Then when the user creating the Production Order using CO01 can implement a check if the correct Order type is entered compared to the Order Type in the Production Scheduling Profile. 

Suggestion 2: Create an SAP Table that stores the allowed Order type for Material + Plant combination, and the a User Exit at CO01 creation to check if the combination is allowed. 


---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

User Exit for t-code CO01

How to find out SAP standard User Exit for Transaction code CO01

Check the following link to the Blog Post for the Possible Solution: 

Check the following link to the Blog Post for the Possible Solution:


---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Thursday, November 23, 2023

SAP MM - Create PO and Message Output (Fiori App)


 click "here" to view Presentation

SAP Acronyms (Part 11)

 

"What is SAP ?"
Lets have some light moments before we
Login to a SAP system
comes  Monday morning


Smiles and Pains
Shoot all Programmers
Solutions against Progress
Some ambiguous Programs
Systems against People
Sorry and Pray
Seamless and Painful
Silly altered Programs
Sick arrogant Professionals
Suck all Profits

Q&A in Class (2023-11-22) S4H00

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PS Internal Work Time Reporting

The scenario is about SAP Project System (PS) Internal Work Time Entries to be billed to the Customer.

A possible solution will be using a Sales Order (order type PS1 in ECC or user define order type with configuration for "RRB") for Resource Billing for the SD-PS integration using "(RRB) Resource -Related Billing":
  1. Create Sales Order with an order item (for example, standard order or repair order) that is account assigned to a WBS element in a customer project.
  2. The WBS element to be account assigned to the order item on the Account Assignment tab page.
  3. Enter a Dynamic Item Processor profile (DIP profile) in the tab strip Sales B for the order item.
  4. If you maintained the Dynamic Item Processor profile in a way so that the system takes the actual cost totals records as the source for the dynamic items.
  5. The system sorts the dynamic items according to the SD order items and determines the price of the billing request using SD Pricing . In this way the SD Billing will be based on the DIP Items Actual Costs.
Here are online and Blog Posts related to DIP and Resource Billing:

Refer to the following online help and Blog Post:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SAP Modules Abbreviations

So, what is MM-PUR? This is an abbreviation to refer to SAP Modules (or Sub Modules). 

eg: 
MM-IM is Materials Management - Inventory Management
MM-LIV is Materials Management - Logistics Invoice Verification
SD-SLS is Sales & Distribution - Sales order Processing
PP-BD is Production Planning & Execution - Basic Data
PP-S&OP is Production Planning & Execution - Sales & Operations Planning
PP-LTP is Production Planning & Execution - Long Term Planning
PP-MP is Production Planning & Execution - Master Planning
PP-MRP is Production Planning & Execution - Material Requirement Planning
PP-SFC is Production Planning & Execution - Shop Floor Control
CO-COPA is Controlling - Profitability Analysis
CO-PC-COC is Controlling - Product Cost Controlling - Cost Object Controlling

The following references maybe useful/links:
or Goto the SAP Terminologies blog section





















-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

SAP Project System (PS)

SAP PS (Project System) is an integrated project management tool used for planning and managing projects. This SAP PS module supports the entire project lifecycle from planning to invoicing and settlement. The PS module have integration to other SAP Modules: SAP FI (Financials), CO (Controlling), MM (Materials Management), SD (Sales & Distribution), PP (Production Planning), DMS (Document Management System), VC (Variant Configuration), (PM) Plant Maintenance etc. 

Components of SAP PS includes the following:
  • PS - Project Structuring
  • PS - Document integration (PS Text and integration to DMS or Document Management System)
  • PS - Notification (Claims)
  • PS - Time Scheduling and Capacity Evaluation
  • PS - Cost Planning (including Easy Cost Planning)
  • PS - Revenue Planning 
  • PS - Budgeting (including integration to FI-IM Financials - Investment Management)
  • PS - Procurement of Materials and Services
  • PS - Confirmation of Internal Project Activities
  • PS - Billing (including Resource Related Billing)
  • PS - Project Progress Analysis
  • PS - Period End Closing  and Settlement
  • PS - Reporting (Structures, Logistics, and Accounting)
Some references to overview of SAP PS (Project System):

or Goto the PS blog section




















-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Friday, November 10, 2023

SAP SD - Advanced Return Order's "Return Overview" Status

CLICK here to view the Presentation

SAP SD - "Customer - 360° view" FIORI App (2023)


 CLICK here to view the Presentation

Q&A in Class (2023-11-10) S4SD1

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

"Customer - 360° view" FIORI App

The App is created for internal sales representative, where the sales representative can gain a comprehensive overview of the business documents associated with specific customers. The sales not only can check the details of business documents that were recently created for a specific customer but also displays aggregated data for sales documents, billing documents, and service documents for a certain period of time.

You can find information about this APP in https://fioriappslibrary.hana.ondemand.com/Customer360view-Version2

(The app access wasn't available at date of S4SD1 class Exercise 19, this presentation will use the "Manage Sales Order" Fiori App to demonstrate some aspects of the Fiori App)

Click SAP SD - "Customer - 360° view" FIORI App to check the Presentation


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

"Returns Overview" Processing status in Advanced Return Order

Is it possible to Manually set to "Complete" status in the "Advanced Return" Sales Order with "Process Incomplete"? 
The simulation done in the Blog Post link below try to show the impact of the "Return Overview" Page's Status to the Advanced Return Order Header and Item Status. 
Initial Conclusion based on today's Simulation is the "Return Overview" Status cannot be changed manually to CLOSE/COMPLETE status, and it looks like it is governed by the Processes completed. However, it does not impact the Advanced Return Order's Header and Item Status. 

"Advanced Return Management" or "ARM" component was released in SAP ERP with option to integrate with the warehouse storage processes in SAP Extended Warehouse Management (SAP EWM) to manage returns items on storage bin level. The inspection of returns items is fully supported by the Quality Management (QM) component of SAP EWM although there is also the "Simplified Inspection" offered within "ARM". 

The following is the Blog Posts relating to the Status question:

Note: as for Advanced Return Management application for Purchasing will be creating a Blog Posts when time and SAP system is available.

Useful links: 
Advanced Returns Management (help.sap.com)
Advanced Returns Management for Customer Returns (help.sap.com)


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

EWM Wave Creation Issue

This issue is not part of the S4SD1 syllabus as the course only covers S4 SD and no relation to EWM. 
Issue description: 
User 1 uses Filter criteria "XX" to create WAVE (for SO#1, SO#2)
User 2 uses same Filter criteria "XX" to create WAVE (for SO#3, SO#4)
Both Users are performing the Tasks almost at the SAME TIME. 
System behavior ends up creating 2 WAVEs
However, the requirement is to CONVERGE the results into 1 WAVE. 
Suggestion: 
Standard behavior in the System generating 2 WAVEs is the most logical and should remain the SAME 
even if SAP has a feature to combine. 
The reason is very simple, it is clear cut Area of Responsibility in 
WAVE 1 for User 1 and WAVE 2 for User 2
There is then no argument that my Orders are in your WAVE, and that is now your problem. 
So, for practicality and clear responsibility cut-off, should remain status quo. 
So that there no arguments later of whos' responsibility for which WAVE. 

Useful links:


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

MRP Live application for non Manufacturing

This question is not part of the S4SD1 syllabus as the course only covers S4 SD and no relation to MRP runs of MRP Live. 

MRP Live can be executed via MD01N or a Fiori App "Schedule MPR Run" and it can be used for 
both Classical and Advanced Planning as the Program will recognize if the material is setup for MM-MRP, PP-MRP, or even PP-Advanced Planning. You can also use it for Single-level MRP run for a group of Materials (for example a group of Re-Order Point Materials) which may not necessary be for the Manufacturing scenario. 

MRP Live flexible as if you have a BOM and only the Header is activated for Advanced Planning, and some higher-level Sub-Assembly for Classic Planning but MPS item, and some components are MRP items as well as not Advance Planning, plus other components are set with MRP type for MM-MRP; the program will be able to cater for ALL the above Material. However, to understand the Calculations; the user must be understand the Material Master MRP1,2,3,4 views plus the Advance Planning views parameters as well as MRP configuration parameters. 

I suggest to look at the following Blog Post (as a start): 
see links: 
or Search for "MRP Live" in my Blog

Useful Links:
Working with MRP LiveS/4HANA Classical MRP vs MRP Live


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Flexible Workflow

This question is not part of the S4SD1 syllabus as the course only covers S4 SD as the Flexible Workflow concept was released for Material Management. The flexible workflow allows you to define approval processes for documents in Sourcing and Procurement according to your requirements and has been introduced in SAP S/4HANA as a set of enhancements for the SAP Business Workflow. By using the flexible workflow, you can simplify your configuration.

The Classic Release Strategy can still be used in S/4HANA, and activation of Flexible Workflow is dependent on Document Type. Therefore, in the same instant, some Document type can still use the Classic Release Strategy and some Document type can activate for Flexible Workflow. Until today, thre is no news if SAP is going to remove the Classic Release Strategy in S/4HANA systems. 

I suggest to look at the following Blog Post (as a start): 
see links: 

Useful Links:
How to Configure the Flexible Workflow for Purchase Orders (help.sap.com)


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

S/4HANA Credit Management

SAP Credit Management solution in SAP S/4HANA is introduced as a "Company-Wide Credit Policy" to help run a "Central Credit Management system" in a Distributed System Landscape. Hence, the Credit Manager can monitor a particular customer’s credit exposure from within one central system.

Somethings to take note in S/4HANA:
  • The classic credit management (FI-AR-CR) is no longer available as part of SAP S/4HANA, The functional has been enhanced and replaced by the SAP S/4HANA is SAP Credit Management (FIN-FSCM-CR). 
  • You can activate/deactivate SAP Credit Management by implementing BAdI UKM_R3_ACTIVATE. SAP S/4HANA 1610 product version and above, SAP Credit Management is implemented as standard, decision to deactivate will turn off the functionality completely.  
  • In SAP Credit Management (FIN-FSCM-CR), Customer Credit Master data is centralized managed by Business Partner using BP Role: UKM000 Credit Management via "Credit Segment" (New in S/4). The "Credit Control Area" as an Enterprise Structure unit in FI is still active and part of the setup together with "Credit Segment" for Credit Check. 
I suggest to look at the following Blog Post (as a start): 
see links: 
Credit Management Overview Highlights

Useful links: 
SAP Credit Management (FIN-FSCM-CR) (SAP Online Help)SAP Credit Management in S/4HANA


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

iDoc vs API

SAP interfaces allow any other software and other solutions to exchange data with the SAP system. Each available interface for exchange of data has advantages and disadvantages.

As of today (November 2023), there are No News from SAP if any of the above interfaces are to be Obsoleted by SAP.

The IDoc (Intermediate Document) is an SAP file format. It is intended for transfer of transaction data. The structure of an IDoc is prescribed by the IDoc type and defines the exact length and position of fields in the file. The IDoc is divided into a header line, any number of data segments and status records. In contrast to the RFC interfaces, communication via IDocs is always asynchronous. The sender creates an IDoc with data according to the specification of the IDoc type and transfers it to the target system. The receiving system accepts the IDoc and inserts it into the processing buffer for IDocs, from which the documents are processed successively. IDocs are a very old and proven method of communication and are especially suitable for transferring master data and posting records. mature, robust, efficient. I don't see any technical reason why SAP would kill IDocs in S/4HANA. Out of experience, they are still there in S/4HANA on premise and they are doing fine. So far as of today, there are no mention if IDoc is to be discontinued in the latest 2023 S/4HANA simplification list or in S/4HANA compatibility scope. There, the IDoc structures used for SAP R/3 or ERP ECC will continue to be available for connecting SAP S/4HANA at the present or near future. So, IDoc may not become obsolete any time soon as all transactions required for processing EDI documents are made available as APIs yet.


Above is a comparison of SAP IDocs with SAP APIs (Version 1809) for connection between SAP ERP and an EDI solution.

Refer to the Expert views below: 

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------













S/4 ML + BoT + PA + RPA + WfA

 

Wednesday, November 8, 2023

Verify Structure of Org Model for CS Cloud

 
click "here" to view the Presentation

Question no 3982 : Price in Purchasing Info Record

In SAP Materials Management in ECC6 EhP8, in which of the following circumstances where the Purchasing Info Record is created without the Price ?

(only one answer)

A) Quotation.
B) Purchase Requisition.
C) Purchase Order.
D) Contract.
E) Scheduling Agreement.
.

Answer: C

A, D, E) Quotation, Contract and Scheduling Agreement allows to generate or update Purchasing Info Record Condition Records.
B) Purchase Requisition has no ability to create or update the Purchasing Info Record.
C) When a Purchase Order is saved and expected to Create the Purchasing Info Record (Info Record does not exist at time of PO creation); for such case, the Price Condition of the PO is not copied over to the Info Record.





Wednesday, November 1, 2023

Question no 3981 : MRP run with or without Lead Time Scheduling

In SAP Production Planning and Execution, an MRP will use the In-house Production time or Lot-size dependent Lead times in the Work Scheduling view in which of the following circumstances ?

(more than one answers)

A. When Routing is not found.
B. When BOM and Routing both were not found.
C. When Scheduling mode is "1" Basic dates in MD01 or MD02.
D. When Scheduling mode is "2" and both BOM and Routing were not found.
E. When Scheduling mode is "2" and Routing is not found.
.

Answer: A, C, E

In MD01, MDBT or MD02, the Scheduling selection field allows to shows either "1" or "2":
  • "1" Basic date dictates MRP run will use either In-house Production time or Work Scheduling view's Lot size dependent data for scheduling.
  • "2" Lead time scheduling dictates the system will try to find a Routing for scheduling but if a Routing is not found then it will revert to use either In-house Production time or Work Scheduling view's Lot size dependent data for scheduling.

SAP SD - Manage Sales Plan (S/4)

CLICK here to view the Presentation

SAP-MM Procurement Process (Stock Transport Order) Fiori and S/4 Backend (2023)

.