--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Customer - 360° view" FIORI AppThe 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
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.
The following is the Blog Posts relating to the Status question:
Click SAP SD - Advanced Return Order's "Return Overview" Status (this demo is without EWM)
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)
Credit Management Overview Highlights
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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:
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:
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.
.jpg)
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:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.