Saturday, September 30, 2023
Thursday, September 28, 2023
Wednesday, September 27, 2023
.jpg)
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:
- SPRO: MM - Inventory Management and Physical Inventory - Authorization Management - Authorization Check for Storage Locations
- 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:
- 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.
- 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.
- 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)
- 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.
- 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)
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
- 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).
- 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.
- 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.
- 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:
- SAP Support - SAP General Ledger Migration
- SAP Press - SAP General Ledger: Preparing for a New G/L Migration
- ERPfixers video - Migration Options for New G/L on S/4 HANA
- SAP Insider - Technical Guide for Migrating SAP General Ledger Data for SAP S/4HANA
- SAP Notes 1600481 - Migration on basis of Special Purpose Ledger
- SAP Notes 1592904 - FI consistency check in advance of migration to NewGL
- SAP Notes 1558185 - Special features during migration to new general ledger
- SAP Notes 1555535 - FAQs: Migration of PCA Report Painter reports to NewGL
- SAP Notes 1467114 - Open item total not checked against carryforward
- SAP Notes 1171402 - Compatibility IS-M/SD with General Ledger Accounting (new)
- SAP Notes 1072121 - New general ledger migration: What is covered by Support?
- SAP Notes 1039752 - New G/L migration: Restrictions and important information
- SAP Notes 1014369 - New G/L migration: Availability of Development Support
- SAP Notes 1014364 - New G/L migration: Information, prerequisites, performance
- SAP Notes 824995 - LCC: Gen. questions/answers about local currency changeover
- SAP Notes 812919 - SAP ERP new general ledger: Migration
- SAP Notes 672255 - Shortened fiscal year/changing fiscal periods
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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:
- 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.
- 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.
- 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.
- 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.
- Another possible solution is stop the backflushing go to zero stock is to set termination of backflushing when not enough quantity:
- Refer to this Blog Post: SAP PP - Backflush Control
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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?
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.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Sunday, September 24, 2023
Question no 3978 : the use of Allocation Structure in Cost Object Controlling
In SAP Controlling, the Allocation Structure is used in which of the following process ?
(only one answer)
A. Settlement.
B. Overhead cost calculation.
C. Joint Production costing.
D. Variance calculation.
E. ABC costing.
.
Answer: A
During settlement, costs incurred under the primary and secondary cost elements by a sender are allocated to one or more receivers. When you settle by cost element, you settle using the appropriate original cost element that debit the order or another cost element can be sued; this depends on the allocation structure. Therefore, at the settlement process; the settlement cost element in the allocation structure will be used for the settlement process.
An allocation structure comprises one or several settlement assignments. An assignment shows which costs (origin: cost element groups from debit cost elements) are to be settled to which receiver type (for example, cost center, order, and so on).
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
(only one answer)
A. Settlement.
B. Overhead cost calculation.
C. Joint Production costing.
D. Variance calculation.
E. ABC costing.
.
Answer: A
During settlement, costs incurred under the primary and secondary cost elements by a sender are allocated to one or more receivers. When you settle by cost element, you settle using the appropriate original cost element that debit the order or another cost element can be sued; this depends on the allocation structure. Therefore, at the settlement process; the settlement cost element in the allocation structure will be used for the settlement process.
An allocation structure comprises one or several settlement assignments. An assignment shows which costs (origin: cost element groups from debit cost elements) are to be settled to which receiver type (for example, cost center, order, and so on).
Allocation Structure can be found in the Settlement Profile.
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
Friday, September 22, 2023
Thursday, September 21, 2023
Wednesday, September 20, 2023
Sunday, September 17, 2023
Wednesday, September 13, 2023
Tuesday, September 12, 2023
Sunday, September 10, 2023
Question no 3977 : Overhead Group, Overhead Key, and Origin Group for Costing Sheet
In SAP Product Cost Planning, the ____________ in the Material Master costing view is assigned to the ______________ in the Customizing where in the Costing sheet, the _____________ will be linked to an Overhead rate to determine the Overhead calculations.
(only one answer to fill in the blank in sequence)
A. Overhead Group, Overhead Key, Overhead Group
B. Overhead Group, Overhead Key, Overhead Key
C. Overhead Key, Overhead Group, Overhead Key
D. Overhead Key, Overhead Group, Overhead Group
E. Origin Group, Overhead Key, Overhead Key
Answer: B
Normally overhead key is created and linked to overhead group. This overhead group is assigned in the material master record. surcharge rate is maintained for overhead rate with dependency of overhead key.
(only one answer to fill in the blank in sequence)
A. Overhead Group, Overhead Key, Overhead Group
B. Overhead Group, Overhead Key, Overhead Key
C. Overhead Key, Overhead Group, Overhead Key
D. Overhead Key, Overhead Group, Overhead Group
E. Origin Group, Overhead Key, Overhead Key
Answer: B
Normally overhead key is created and linked to overhead group. This overhead group is assigned in the material master record. surcharge rate is maintained for overhead rate with dependency of overhead key.
Saturday, September 9, 2023
Q & A in class (2023-09-08) PLM400
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Inspection Type "03" is for In-Process Quality Inspection and an Inspection Lot is generated when the Production Order is Released. The MIC (Master Inspection Characteristics) of this kind of Inspection Lot is from the Material Routing (likely with Control Key PP06).
For this: usually the following setup
- Routing Header with Inspection Point "150".
- Routing Operation detail with either Qty or Time (eg: every 10pc or every 30min) which means if Production of is 100pc for 3 hours, the system will either generate 10 containers (10pc each) or 6 contains (every 30min).
- Operation is assigned with Control Key "PP06" with MIC.
- the MIC optionally can be SPC characteristics.
- For SPC MIC, a Sampling Procedure with Valuation Mode "SPC Inspection" plus a desired "SPC Criterion" when assigned to the MIC in the Routing Operation.
RR is expected for the In-Process Inspection Lot where the RR entered are plotted for SPC-based MIC for Process Control purpose. Out of tolerance can trigger Defect Recording and QM Notification for Countermeasure initiation. BUT Usage Decision for such type of Inspection Lot do not result in any Inventory Movements.
Refer to the following Blog Post for the Process step for Inspection Type "03":
Inspection Type "04" is Goods Receipt Inspection Lot is for Inspecting Products AFTER the Production Order Goods Receipt, Inspection Lot is generated after MIGO of the Production Order. Standard SAP has Usage "5" assigned to the Inspection Type "04" and an Inspection Plan with Usage "5" is expected.
The process flow for Inspection Type "04" for Production Order GR-Inspection Lot is similar to Inspection Type "01" for Purchase Order GR-Inspection Lot.
Refer to the following Blog Post for the Process step for Inspection Type "04" Inspected Lot for Goods Receipt Production Order:
Inspection Type "04" configured for "Early Inspection for a Goods Receipt" is for Inspecting Products BEFORE the Production Order Goods Receipt, to active this Inspection variant will have to set the "ControlInspLot" Indicator "Y" as below
In this Inspection variant, the Inspection Lot is generated when the Production Order is Released. In this case, when Production almost completed the Batch (Lot) and before the GR step, Result Recording will be done on the Inspection Lot BUT do not perform any UD.
Then, MIGO is to be perform to the Production Order which will receive into QI stock; and next, UD will be entered to the Inspection Lot and decide if the QI stock should be transferred to UR. Hence, the UD step will automatically move from QI to UR.
Therefore, in this case; Inspection is done before the GR step.
Wednesday, September 6, 2023
Question no 3976 : PP objects without a Plant
In SAP Production Planning and Execution, which of the following PP object can be created without a Plant ?
(only one answer)
A. CS01 Create a Bills of Material.
B. CA01 Create a Routing.
C. MM01 Create a Material Master for Planning and Execution.
D. MD61 Create Planned Independent Requirement.
E. CO01 Create a Production Order.
Answer: A
A) A BOM can be created without a Plant which is called BOM Group, which later can be assigned to one or more Plants.
B) A Routing can be created without a Material but must have a Plant, which later the Routing can be assigned to one or more Materials.
C) The MRP view and Work Scheduling data view for Planning and Execution respectively are both at the Plant level.
D) A Planned Independent Requirement must be created for a Plant and Material.
E) A Production Order must be created for a Plant but need to have a Material.
(only one answer)
A. CS01 Create a Bills of Material.
B. CA01 Create a Routing.
C. MM01 Create a Material Master for Planning and Execution.
D. MD61 Create Planned Independent Requirement.
E. CO01 Create a Production Order.
Answer: A
A) A BOM can be created without a Plant which is called BOM Group, which later can be assigned to one or more Plants.
B) A Routing can be created without a Material but must have a Plant, which later the Routing can be assigned to one or more Materials.
C) The MRP view and Work Scheduling data view for Planning and Execution respectively are both at the Plant level.
D) A Planned Independent Requirement must be created for a Plant and Material.
E) A Production Order must be created for a Plant but need to have a Material.
Subscribe to:
Posts (Atom)