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

Wednesday, September 27, 2023

Q & A in class (2023-09-27) S4H00

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

Storage Location De-activated and Authorization objects to allowed Movement for De-activated Storage Location, Some storage Location previously active to retain histories but disallow goods movement for that Storage Location. In order to enabled this requirement, a combination of 2 settings are recommended: 
  1. SPRO: MM - Inventory Management and Physical Inventory - Authorization Management - Authorization Check for Storage Locations
  2. Authorization Object M_MSEG_LGO
Refer to the following Blog Post for the details setup steps: 

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

Production Order creation without Batch entered at the Component and subsequent entry of Output Batch displays a dialogue with option to Exit only AND a Message box without Message number

Suggestion:
  1.  The dialogue without a "Cancel" button (only "Exit") and Message button without Message number could be the result of a User Exit and not standard SAP. 
  2. Check the following User Exit
    • PPCO0001  Application development: PP orders
    • PPCO0002  Check exit for setting delete mark / deletion indicator
    • PPCO0003  Check exit for order changes from sales order
    • PPCO0004  Sort and processing exit: Mass processing orders
    • PPCO0005  Storage location/backflushing when order is created <------
    • PPCO0006  Enhancement to specify defaults for fields in order header
    • PPCO0007  Exit when saving production order
    • PPCO0008  Enhancement in the adding and changing of components
    • PPCO0009  Enhancement in goods movements for prod. process order
    • PPCO0010  Enhancement in make-to-order production - Unit of measure
    • PPCO0012  Production Order: Display/Change Order Header Data
    • PPCO0013  Change priorities of selection crit. for batch determination
    • PPCO0015  Additional check for document links from BOMs
    • PPCO0016  Additional check for document links from master data
    • PPCO0017  Additional check for online processing of document links
    • PPCO0018  Check for changes to production order header
    • PPCO0019  Checks for changes to order operations
    • PPCO0021  Release Control for Automatic Batch Determination
    • PPCO0022  Determination of Production Memo
    • PPCO0023  Checks Changes to Order Components.
  3. If a User Exit has been implemented resulting in the dialogue with only a "Exit" button; one suggestion is to review the dialogue triggered via the User Exit check to insert an extra button "Cancel" button to avoid exiting the Production Order to allow the Planner to proceed to enter Batch for the Component before re-entering the Output Batch. (Rather than the current "Exit" where the Planner have to re-enter all data gain)
  4. One of the reason why a User Exit has been set for this check implemented is to ensure Batch must be entered for the Raw Material before the Production Order is SAVE and Released. IF the Production Order is allowed to be SAVE and Release without the Raw Material Batch, then Backflushing will be a Problem. That is probably the reason why the User Exit was implemented to stop the Production Order creation without a Raw Material Batch. 
  5. However, there is an option in PP configuration to deal with the issue without such a User Exit:
    • Entry 1 or 3 is maintain in material Master of all the BOM components in the MRP2 view.
    • T.Code OPJK to select Order type and Plant combination with Batch Assignment select value 3 (No release if without batch Assignment)
    Refer to the following Blog Post for the details demonstration of the above PP configuration to stop Release of Production Order without a Component or Raw Material Batch:
    to-be-posted via


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

    Migration from ECC to S/4HANA with New G/L activation New GL functionalities are part of ECC 6.0 version with optional activation BUT it is a mandatory component in S/4HANA.

    The New GL concept covers all the functions and requirements in one place providing the functions
    1. Document Splitting - for each financial account document, document splitting functionality applies account assignment information (profit center) to the non-assigned GL accounts (Vendor, Customer and  Tax line items in particular and any other accounts not assigned due to any reasons, in general).
    2. Balanced books (zero balance) by dimensions like Profit Center, segment, Business area - this functionality ensures drawing out balance sheet at Profit center level, segment level or business area level.
    3. Real-time integration of Financial Accounting with FI - where Real-time integration of CO with FI is ensured.  This ensures transfer of cross-entity controlling postings to general ledger in real time. This transfer allows continuous reconciliation of Cost Accounting books with financial books and removes the need for any subsequent reconciliation.  
    4. Parallel Ledgers - allows different Ledgers for different accounting principles. For example: one ledger for Local GAAP, one for US GAAP, one for IFRS, one ledger with different fiscal year other than the one being used in the company code etc.  
    Migration from Classical G/L to the New G/L is not a flip of the switch but requires a proper to manage multiple Activities as below:
    • New GL Migration
    • Activation of Migration Cockpit
    • Document Splitting
    • Activation of Segment Reporting
    • Activation of Parallel Accounting
    • Etc.
    Note the following supporting information about new G/L implementation:

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

    Backflushing issues resulting in MAP set to zero when stock become zero and COGI happens example material is Gas in a BOM to be backflushed when physical stocks are in the tank for backflush but goods receipt not yet completed due to delay in documentation from the supplier. Standard lot size is 1000 and UOM is KG but MAP is 0.55 per kg and BOM definition is using 0.555kg per 1000 production output (numbers are estimate from discussion). Whey does this happen; meaning why when bacfklush to zero qty into COGI and the MAP is set to 0.00 by SAP ?

    Few suggestions:
    1. Certainly the main problem is why they is delay in information from the supplier to provide on-time system update of the incoming gas qty in KG into SAP resulting in Production can backflush the physical qty while system qty is not in the system resulting in COGI. For sure, when the supplier replenish the gas into our tank, they should already be available information on the replenishment qty plus some documentation like a DO; because the tanker surely has a gauge to record what pumps out of the tanker to the gas tanks! 
      • I am pretty sure that operationally it is possible to provide the filled-up quantity more timely manner to allow SAP to update the qty received into the tank for backflushing correctness. 
      • I suggest to discuss with the gas vendor and setup methods for a timely manner of the information which for sure is doable as nothing is impossible because even if the tanker coming in has no gauge; there is always weight bright for coming in and going out for determining the replenished qty. 
    2. The above should be the main priority method to address this issue. As another solution is to try to change the UOM, qty per in the BOM etc which even is possible; the root cause of the COGI due  to delay of info for GR qty is not addressed; then COGI will continue to happen anyway which does not make sense. 
    3. Solve the operation problem of timely entry of the GR qty rather than trying to change SAP data as the root cause is the operation issue.
    4. However, to do the technical checking of the appropriateness of the UOM in Material, UOM in BOM, appropriate Base qty etc. is possible with first data analysis, system simulation, and some time to look at re-designing the data in SAP to eliminate the MAP become zero problem when stock goes to zero. 
    5. Another possible solution is stop the backflushing go to zero stock is to set termination of backflushing when not enough quantity:

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

    MCHBH table vs MEBWH table Stock inconsistencies issue happens for some selected material usually during Financial closing. Why? 

    Background information 
    • MCHB is up-to-date current Batch Stocks data (Valuated stock with unrestricted) (current period)
    • MCHBH is Batch Stocks History data (previous period)
    • MBEW is up-to-date current Material Valuation data (Total Valuation Stock) (current period)
    • MBEWH is Material Valuation History data (previous period)
    Whey MCHBH against MBEWH are not matching?

    Since MBEWH table is referring to total valuated stock and MCHBH table is referring to valuated stock with unrestricted; therefore, it is possible that the values in the 2 tables are different.

    It is normally that they will be instances where it appears historic records were not appropriately updated to the MBEWH and MCHBH tables and this is a known scenario in SAP. While MBEWH is history of current, the updating to MCHBH in interesting: for example, If you have record in MCHB with period 9 then batch Quantity. Change happened in this period, but the corresponding MCHBH record you will find in 08 period MCHBH record is written in last period.

    It is usual that reconciliation is a necessary work step when sometimes the 2 tables don't match exactly.


    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    at
    Labels:

    No comments:

    Post a Comment

    Note: Only a member of this blog may post a comment.

    Subscribe to: Post Comments (Atom)