Knowedge Sharing on SAP – Supply Chain Modules
Satheeshkumar 
Generally we have some standard programs for the few of the T.codes.
This program names are very important and useful , when we plan to run the T.codes in the background
This Blog will detail out some of the programs / Tcodes..
T.code – Program Name
MS66 – RM60CH00
COGI- CORUAFFW
MD74 – RM60RR20
MD75 – RM60RR30
MD76 – RM60RR40
Note: I will keep adding to this Blog.
Since we are in the end of the year , i thought to write some few things that has to be generally ensured as part of the year ending activities.
I am listing down few of them which are on my checklist..
A.Calendar:
* Calendars are very important one to be checked as part of the year ending activities.
* Check if the Holiday calendar and the Public holidays are extended to the next year.
1.Factory Calendar – SCAL
2.Shipping Calendar – OVXD
3.Planning calendar -MD27
B.Number Ranges:
Ensure that you have enough number in the buffer. Below are the few of the list of number ranges can be checked.
1.Define number ranges for orders -CO82
2.Define number ranges for confirmations – CO80
3.Define number ranges for reservations-CO83
4.Define number ranges for operations-CO81
5.Define number ranges for capacity requirements -C084
6.Define Number Ranges for Planning Run -OMI2
7.Define Number Ranges for Manual Processing-OMI3
C.Back Ground Jobs:
1. Check if any Back ground jobs has to be extended.
2. You can use the Table TBTCO.
D.Activity Price:
1. Even though the complete ownership of this activity is with Controlling team , it will be good for us to cross check if all the activity types are having the cost for the next period
2. To check this quickly you can use the KP26, list out your Cost centres / Activity types and check it.
In case if your Fiscal Year is also your end of calendar year then many FI Steps will be there and Links for them are
1. https://blogs.sap.com/2008/07/09/year-end-closing-in-asset-accounting-best-practices/
2. https://answers.sap.com/questions/6869746/year-end-activities—fico.html
This is not the End of the List, but covers maximum important activities, i will keep modifying the same.
Wishing you all Advance New year Wishes !!!
The below will be the list of Function modules which will be useful !! I will keep this list added !!
1. VC_I_GET_CONFIGURATION
* This will help you to get the configuration parameters of the configurable material
2. CO_BT_GET_ALL_VORNR_IN_ORDER
* This will Help you to get the Operation details in the Production order.
3. MD_STOCK_REQUIREMENTS_LIST_API
* This will help you to get the MRP Stock requirement list.
* Most of the details that are seen in the MD05/07 Can be extracted from thism
4. BAPI_CLASS_GET_CHARACTERISTICS
* In case if you need to get the characteristics and the values for the Class ( Like 300 /023) etc, then you can use this FM
* You need to give the Class and the class type
* It will give you the output with characteristics with / without values.
5. BAPI_PRODORD_GET_LIST
* You can get the list of the Production orders.
6.CS_BOM_EXPL_MAT_V2
* This will help you to get the list of Materials in a BOM
7. Planned Independent Requirement:(Create,change,Display)
The below 3 FM will help you in the PIR Create, Change and Display.
BAPI_REQUIREMENTS_GETDETAIL
BAPI_REQUIREMENTS_CHANGE
BAPI_REQUIREMENTS_CREATE
8.CO_61_CHECK_ORD_TO_SDOC
* This will help to get the planned order @ sales order leve.
9.CUCB_GET_CONFIGURATION
* Get the configuration.
10.BAPI_PRODORD_GET_DETAIL
* Get the Operation in the Productoin order.
11. Copy the variants fro a program
RS_COPY_SELECTION_SETS
2. BKK_ADD_WORKINGDAY – Add working days
This Blog will bring out some basics of Discrete Vs Repetitive manufacturing as a Snap Shot.
Discrete Manufacturing:
1. When production is done Based on Orders.
2. Cost is collected at Order Level.
3. Collection of cost
4. Complex Routing/Bom( Like Variant Configuration)
Repetitive Manufacturing:
1. When Production is done Periodically( Same product Produced for over period of time)
2. Simple Back flushing is Planned.
The below are few other points that are differentiate them.
Master Data
1. Material Master
Work Scheduling View:
Discrete: You need to have the Work Scheduling View activated for this.
REM: Work Scheduling is not Required.
REM Profile:
Discrete: No Rem Profile is required.
REM: REM Profile is Mandatory.
2. Production Version
Discrete: It is Optional
REM: It is Mandatory
3. Product Cost Collector:
Discrete: It is Not Required
REM: It is Mandatory , it is the one which collects all the cost.
4. Settlement
Discrete: Settlement is done at the Production order level.
REM: It is at material Level.
5. Work Order.
Discrete: Production order are mandatory.
REM: No Order,
6. Confirmation
Discrete: confirmation is done at Production order Operation level or at Order level.
REM: Confirmation are done at production version /Planned order level.
7. Capacity Planning
Discrete: Done with CM01,02 etc,
REM: Need to be done with MF50 Planning table.
8. Shop Floor Paper.
Discrete: Can Create shop floor Print.
REM : No Standard Shop floor Paper, need to do Custom Development if Required.
9.Order Information System
Discrete: Has Detailed order information
REM: No detailed list.
Few other Links are As below.
In SDN
Note: Will Keeping adding this, also any of your comments, Views can be posted n Comments.
Intro:
In this Post we will review the In process inspection of the REM scenario. I like to be very specific on particular inspection type since the incoming inspection( 05 Inspection type) and the Finished Goods Inspection ( 04) are same as discrete manufacturing only.
But the In-Process inspection the lot generation is unique for the Rem Scenario.
In-Process inspection:
*Like the other manufacturing type REM manufacturing cycle also requires to monitor the In Process for the quality control Module.
* In discrete when the production order is created a lot will be generated, but in case of the REM we need to create one inspection lot for each production version.
* The results recording can be done for certain open periods like week, month year based on the requirement.
Master Data:
QM – Master Data:
* MIC- Master inspection Characteristics ( QS21/22/23)
* Inspection Method- ( QS31/32/33)
* Sampling Procedure( QDV1/V2/V3)
PP-Master Data:
* Material master
# In this QM view should be active
# Inspection Lot type 13 Should be activated.
* Work centre
* Routing – In routing we need to maintain the required MIC in the operations.
* Production Version.
Transaction :
* Once when we have all the required master data set up, we are ready to create the Inspection Lot for the In process.
* For this You have to enter the T.code – MFPR
* In this t.code you need to provide the Plant, Material,Production version.
* Once when you enter them and press f8.
* It Will take you to a new screen wtih Process Inspection Lot for Production version.
* Here you need to select the check box for the required Production version and Hit create inspection lot.
* After this you can see the Inspection Lot Generated.
Results Recording;
* Once you have the Inspection lot you can check for them in the QA32.
* The results recording is common.
* Once when you decide to close the Inspection lot then you can take the usage decision, til then you can record the results with the Inspection Points.
* Once Usage decision is taken to create the results recoding you need to follow the same process.
The above is simple flow to understand the REM In process inspection
In this post I will Explain a simple REM cycle for the PP Module.
Master data:
************
* Material Master:
* In this you need to have the REM indicator activated.
* A Rem Profile attached
* Production version with BOM, routing, production line( it is nothing but a work centre)
REM indicator activated.
* BOM
* Routing( Routing or rate routing both will work fine for the rem)
* Production version.
Configuration:
*************
1. REM Profile
Process Flow:
***********
1. First Create all the required material master as indicated above.
2. Once this is done now you have to create a product cost collector
* REM- works on the Product cost by period.
* So the Product cost collector is a CO order which helps to collect all the cost at a material /
production version combination to an internal order
* Which later settles the variance against a material
* You can create the Product cost collector with KKF6N
3. during the creation of the Product cost collector it will prompt you to do the Preliminary cost collector- for rem you need to run this one also.
4. Once the above is done , now you have to run the Cost estimate Mark and release the same with CK11N AND CK21(you can reach the help of FICO consultant to complete this process)
5. Once the above is done now the master data and prerequisites are complete and ready for the PLANNING AND CONFIRMATION of the product/material.
6. Now you can maintain the demand in the md61 for the required quantity.
7. Once the demand is maintained and the MRP is run you will be able to work with the REM PLANNING TABLE.
8. One of the best features in the REM is the Rem Planning table
9. This can be accessed with the T.CODE MF50.
10. Here when you try to access the MF50 you have multiple choices to make selections and also restrictions.
11. Inside the planning table you can see 2 major things
a. In the upper section of the planning table you can see the available/ actual capacity
b. In the lower section of the planning table you can see the demand and few other attributes like stock, ROC, Production version etc.
12. This MF50 helps you to make the Planning- the Creation / modification of the planned order are very dynamic in this screen and is well integrated with all the functionalities.
13. Once all the planning is done with the MF50 then comes the EXECUTION ie) our confirmation.
14. In REM production confirmation is called as MATERIAL BACK FLUSH.
15. you can access the Material back flush with MFBF.
16. HERE in MFBF you can have some mandatory parameters like Quantity, material, production version, date etc which has to be given as input , and the system will in turn perform the back flush.
17. the MFBF is single screen which allow you to perform the below function
* Material back flush
* Excess consumption
* scrap posting
* Only activity posting
and few more.
18 Once the back flush is done the stock gets posting
19. You also have cogi/mf47 FOR clearing the post goods movement errors for automatic posting.
Hope the above process flow will be useful for someone to get introduced to REM. Again this is a short glimpse .
You can post your questions as comments , which will be answered by Me.
Introduction:
In my previous posts we have seen on the Kanban for the Inhouse, External procurement, interestingly we do have kanbans for the Customers also.
In the Current manufacturing world the kanban is involved in the full production to sales of a Product.
There are many articles / Case studies / White papers that flows when you google for this topic.
Scenario:
The manufacture produces the material and supplies to the customer in a Kanban container.
This kanban containers is in cyclic movement between the Customer and the Supplier.
Large automobile giants currently are working on this kanban with lot of automation’s.
The manufacture can use REM / Discrete Production method as per the business requirement.
I have taken the example of REM environment.
In this post i will guide you to set up this scenario.
Master Data Requirement:
1. Material Master, BOM, Routing,Workcenter,Production version – All this for the REM setup.
2. The material master should support sales functions
3. Customer Material Information.
4. Kanban Control cycle.
Configuration Pre Requisites:
1. OM11- Inhouse replenishment strategy
* Control Type – as 2-Processing with Planned orders and Cost collector.
* In this Kanban With SD needs to be selected with 1-Delivery what status Full and GI when status is in use.
2. SD- Scheduling Agreement Document type
* You can use BL, check the MRP for Dlv Schedule type to the correct one.
I have worked with A.
Process Flow:
1. Set up the Master data for the FG so that it is ready for reporting Production.
2. Now Create a Scheduling agreement for the FG material.
3. Here in the Forecast delivery Schedule you can maintain few values ( 1000 ea) for next 3 months.
4. The assumption is the Customer gives us a Forecast delivery schedule well ahead of time and periodically sends us the JIT delivery schedule.
5. Once you have set up the scheduling agreement create the control cycle for FG, in this you have to maintain the SD scheduling agreement in the In house replenishment strategy.
6. Once your Control cycle and SD scheduling agreement is ready , the kanban cycle can get started.
7. Now whenever we receive the JIT delivery schedule we wil update the quantity in the JIT delivery schedule of the SD Sched. Agreement.
8. Now let us say the Empty kanban container is received from the customer then during the receipt of this empty container the status of the container will be changed as EMPTY,
* This status change will trigger a Planned order created for the Fg.
9. As the planned order is triggered now the Manufacturing department will be producing the product and filling the container.
* Once the container is Full now the Status will be changed form EMPTY TO FULL.
* This Status change will trigger a DELIVERY to be created for the Scheduling Agreement.
* At the same time a GOODS RECEIPT /ISSUES will be posted for the PLANNED ORDER.
* STOCK Of the FG will be increasd.
10. Now as the container is full now it is ready to be transferred to the customer, so when the container is physically sent to customer place then the status of the container will be changed from FULL TO IN USE.
* This status change will do a PGI for the DELIVERY.
* The stock of FG will be reduced.
11. After this the Billing and other business process can be started.
12. This above process cycle will help you to configure the basic cycle of Kanban for the SD cycle,
13. The below Diagram is for reference.
Kindly Post your querries/ Feedback.
Introduction:
In my previous post we have seen the Kanban for the In house production. In this post
I will be writing about the Usage of Kanban in the External procurement.
In this Kanban we will viewing the usage in the External Procurement for the below procurement types
1.Purchase order.
2.Scheduling Agreement with Delivery schedule.
1. Kanban with Purchase order:
1.1 Master Data Requirements:
1.Material Master ( Procurement type F)
2.Vendor Master
3.Purchase Info Record( ME11)
4.Source list ( ME01)
5.Kanban Control cycle ( PKMC)
1.2. Configuration Requirement:
1. External procurement Strategy- OM12
· In the Control Type – You need to maintain with Purchase order
1.3. Requirement Over view.
· When Kanban Status is set to empty a Purchase order needs to be triggered.
· When the Kanban Status container is Full – A GR needs to be posted
1.4. Process Flow:
i.Create material master for the External procured material
ii.Create a vendor master; maintain the Purchase info record, Source list.
iii. Now Create a Control cycle with PKMC.
iv. In the control cycle maintain the External procurement strategy with
purchase order.
v.Also maintain the Kanban qty, no of kanban etc.
vi.Once the Kanban is done , now you can review the status of the Kanban in the Kanban Board
With Pk13n.
vii.Now the status will be set as wait as this is the initial status,
viii.Now you can right click the container and click the ‘Set next statuses.
ix.Now this will trigger the status to Empty. And you can review the information about this kanban And you can see a replenishment element purchase order has been triggered now.
x.This PO can processed for further actions like PO print, Sending to vendor eTc.
xi.Once when you receive Good, you can go the Kanban board and change the status as “Full”.
xii.Now this status change will post a Goods Receipt against the PO.
xiii.After this the next set of actions like Invoice verification, vendor payment etc can be triggered.
xiv. This cycle of activity can be continued for all kanbans of this kanban control cycle.
2. Kanban with Scheduling Agreement & JIT Schedules.
2.1 Master Data:
i.Material Master ( Procurement type F, JIT Indicator as 1)
ii.Vendor Master
iii. Scheduling Agreement ( Type LPA with JIT Forecast Profile)
iv. Purchase Info Record( ME11)
v.Source list ( ME01) with the Scheduling agreement
vi.Kanban Control cycle ( PKMC)
2.2. Configuration:
i.External procurement Strategy- OM12 with Control Key 7 Summarized JIT calls.
ii.SA Release Creation Profile.
2.3 Requirement Overview:
·When Kanban Status is set to Empty a JIT Call needs to be triggered.
·When the Kanban Status container is full – A GR needs to be posted against this JIT call.
2.4. Process Flow:
i.Create the material master for the externally procured material
ii.Create Scheduling agreement with LPA, Assign Profile and kanban indicator in the item additional data
iii.Assign the SA in the Source list.
iv. Create control cycle and maintain the External Proc Strategy and SA details.
v.Once the Kanban is done , now you can review the status of the Kanban in the Kanban Board With Pk13n.
vi.Now run the MRP run so that the demand triggers some schedule lines( Pre requisite- this is planned in MRP and it has some depended demands)
vii.We need to see the Schedule lines in the MDO4 screen.
viii.Now Release the SLines with ME84.
ix. After this review the status of the container in the Kanban Board PK13N.
x. Now you can right click the container and click the ‘Set next status’.
xi. Now this will trigger the status to Empty. And you can review the information about this kanban And you can see a replenishment element JIT Call has been triggered now.
xii.Again you can change the status from EMPTY to FULL in the same T.code PK13n.
xiii.This status change will do a Goods Receipt for the JIT Call.
This post helps you to do the start up of kanban for the External procurement, Kindly drop in your comments and clarifications. Also I will be posting about the SD-Kanban in the Next post..so keep watching.
kanban-Introduction:
* kanban is one of the manufacturing methods that are used in the most of the manufacturing industries recently.
* In SAP Kanban is used in the different Procurement Process like Inhouse Production, External procurement, & Stock transfer ,
* Currently SAP Has capability of handling the same for the Sales and Distribution as customer kanban also.
* This topic helps the user to configure the kanban in the SAP system for the Production Planning with different procurement Types.
* Generic Master data requirement.
Master Data:
1.Material master
2.Bill of Material.
3.Work Centre
4. Routing.
5. Production version.
6. Product Cost collector(PCC) – For Rem process.
Configuration:
1. OM11-In house production strategy.
2. Supply Area.
3. Rem Profile.
4. production Scheduling profile.
5. All other setting for the production order related process.
1. Strategy 0001- Working with kanbans and PCC
1.1. This strategy works based on the REM planned order.
1.2. So the care on the master data setup with rem profile, Prd versions, product cost collector are all to be verified before we start the setup.
1.3. After we have checked for the master data setup we need to set up the Kanban control cycle.
1.4. Kanban Control Cycle – T.Code – PKMC
1.5. In PKMC – give the Plant, supply area, and you can see a creation indicator to create the same.
1.6. In the control cycle we need to define the kanban container related setting, Like No .of.Kanaban’s, Quantity / kanban container, And also the procurement strategy.
1.7. Here we will be working with In house production strategy.
1.8. There are few other tabs like Flow control, Kanban calculation, print control
1.9. To keep the scenario simple we are not maintain any ting in the other 3 tabs.
2.0. Once you complete this setup you can go to the kanban Board with T.code Pk13n.
2.1. Kanban Board- PK13N.
2.2 This helps you to view the status of the kanban containers,
2.3. Kanban has different status like Empty,Full,in use, etc. We will work with only 2 status like
Empty and Full.
2.4. Status – Empty means- There is is no material inside the Container, Full means – The container is having Full Quantity of material as mentioned in the control cycle.
2.5. PK13N- Now enter the T.code and See the status of the container.
2.6. Generally Whenever we see the container for the first time we will be seeing it as Wait,
2.7. Now we need to change the status as Empty.
2.8. To do this you can see an icon for Full or you can right click the mouse by placing the cursor on the container.
2.9. As you change the status the colour of the container also changes.
3.0. Empty Kanban – Red Color, Full Kanban- Green Color.
3.1. Also when you change the status from Empty to Full – A Goods Receipt is posted and stocks are increased.
3.2. When the status is changed from Full to Empty –
3.3. Now Whenever there is change in the status ShopFloor The same will be done in the kanaban board also, Currently these has been automated with interfacing with RF Scanners also.
2. Strategy 0002- Working with Planned order and PCC
2.1. This Strategy exactly works like that of 0001 described above, The difference is it creates planned order that are visible in the md04 screen.
2.2 These Planned orders are the Replenishment Elements.
2.2. Apart all are Same like the 0001 strategy.
3. Strategy 0003- Working with Production order.
3.1. This strategy creates replenishment element of production order.
3.2. here the scheduling is to be forward scheduling so you need to create a production scheduling profile, which makes forward scheduling and Release the production order immediately as it gets created,else you will get error.
3.3.Apart all the process are similar.
The above is the beginning for someone new to kanban, Kindly leave your comments for any query.
we have seen the Standard SOP in the previous blog,in continuous to that we will review the flexible planning.
Why Flexible Planning?
* SOP has limited features, it has fixed characteristics,Keyfigures and only 3 Planning type.
* In Flexible Planning we can create the characteristics as per our requirement, we can have Sales org,Dist channel, Division etc.
* Keyfigures can also be planned as per requirements.
* Standard SOP does only level By level Planning, But Flexible planning can be done as consistent or level by level also.
we will review the same as step by step.
1. We need to create the self defined infostructures.
1.1. Maintain Self-Defined Applications
* Here we define the applications like Sales,production etc.
1.2.Maintain as Dictionary Structure
* In case if we are not having the required characteristics or keyfigures same has to be created.
* All the required data elements can be created and also maintained in one single structure.
1.3 Self Defined field Catlogs.
* this helps to group the characteristics and keyfigures as required,
1.4 Maintain Self-Defined Information Structures ( MC21)
* Once all the above prerequisites aer done, we can create the Infostructure.
* Generally in the Flexible planning we need to create our own self defined infostrucuture.
* the required characteristics, keyfigures all to be assigned properly.
* The sequence of the Characteristics should be properly arranged.
* Also the planing possible to be selected.
1.5 Info structure planning parameters .(MC7F)
* Once the Infostrucuture is created, the next step is to maintain the planning parameters.
* mostly it will be created as consistent planning.
2.Planning type.
2.1. Create Planning type.(MC8C)
* Planning type is to be created as next step.
* each planning type will be created with reference to the Infostructure only.
* In the planning type Aggregate planing,detailed selection needs to be activated.
* Planning horizon / Standard calculations are to be maintained as per the requirement.
* Also required keyfigures needs to be selected and this will form the planning type.
* Once the planning type is created save it.
* here as discussed in the other blog we can create the required macro and also attach it accordingly.
3.Master Data
3.1. Planning Hierarchy:(MC61)
* First thing to be created is the Planning hierarchy.
* Planning hierarchy is the characteristics values arranged in hierarchy fashions.
* Planning hierarchy is created for each info structure.
4. Planning :
4.1. Create Planning;(MC93)
* First we need to create planning for the required Planning type that we have crated.
* This data to be created at version level.
* In the planning type we can also have few customer functions.
* This customer functions can be activated and can be made to perform as per our requirement.
* once all the planning is done then we can save this.
5. Demand Transfer:(MC90)
* MC90- we can use this transaction to do the transfer of value from one key figure to the demand management.
6. Demand Transfer – mass processing
# All the required steps for the mass processing has been discussed in the previous blog.
I have explained the Flexible planning in high level, it will be helpful for beginners.
let me know if you have any clarifications and feedback