Production order and Process order

[SS15]

Hello,

I am working on a scenario to fetch the Production order details from ECC to MII using JCO action call.

I went through many blogs,

BUT I want clarification to below points (in crisp manner will be appreciated)

1. Difference between Production order and Process order

2. list of BAPI used for both -

Production order and Process Order

3.Significant BAPI

4.Life cycle of Production order like ( Release in ECC --> reflected in MII)

similarly entire cycle for Process Order

TIA,

Shailaja

[muthulingaiah · Accepted solution]

Hi Shailaja,

                Please find  below answers to your post . 

1)      A Production Order is defined as follows:

SAP supports three types of production orders.

i)Standard u2013:The Standard production order is based on the bill of materials(BOM) and you use it to produce a regular production item. You manage material transactions of the regular production process. In addition, you can change components at the production stage. When you open a new standard production order, all the components are filled in automatically.

ii)Special u2013: Use the Special production order to produce and repair items or to perform activities that are not necessarily bill of materials items. For example, repair order for customer equipment cards, or repair order for rejected assemblies. You create special production order components manually.

iii)Disassembly u2013 :Use the Disassembly production order to explode a parent item of the regular product to its child items. You disassemble the product into separate parts, which can then be put into stock and sold. For example, you can purchase a used car, take it apart, and sell the individual components

Once you release a purchase order and goods receipt is done it is converted to production order to initiate manufacturing of the product. Finally the goods are picked and confirmation of production order is done.

Process order: it is used in case for process industry where the BOM may change with each lot or batch .for eg. like in a pharma company every tablet has a batch number which has some different composition . For such Process industry we use Process order we need to define master recipe ,bill of material, resource and production version as master data for process industry .

2) List of BAPI For Production Order

The list of production order bapis are as below:

BAPI_PRODORD_CHANGE : Change Production Order 

BAPI_PRODORD_CHECK_MAT_AVAIL : Execute Material Availability Check for Production Orders 

BAPI_PRODORD_CLOSE : Close Production Orders 

BAPI_PRODORD_COMPLETE_TECH : Technically Complete Production Orders 

BAPI_PRODORD_COSTING : Carry Out Costing for Production Orders 

BAPI_PRODORD_CREATE : Generate Production Order 

BAPI_PRODORD_CREATE_CAP_REQ : Create Capacity Requirements for Production Orders 

BAPI_PRODORD_CREATE_FROM_PLORD : Convert Planned Order into Production Order 

BAPI_PRODORD_CREATE_FROM_REF : Create Production Order with Reference Order 

BAPI_PRODORD_EXIST_CHECK : Check Existence of a Production Order 

BAPI_PRODORD_GET_DETAIL : Output Details of a Production Order 

BAPI_PRODORD_GET_LIST : Output Production Order Header Data in a List 

BAPI_PRODORD_RELEASE : Release Production Orders 

BAPI_PRODORD_REVOKEUSERSTATUS : Reset User Status for Production Orders at Header Level 

BAPI_PRODORD_SCHEDULE : Schedule Production Orders 

BAPI_PRODORD_SETUSERSTATUS : Set User Status for Production Orders at Header Level 

BAPI_PRODORD_SET_DELETION_FLAG : Set Deletion Flag for Production Orders 

BAPI_PRODORD_SET_DEL_INDICATOR : Set Deletion Indicator for Production Orders 

BAPI_PRODORD_WM_MAT_STAGING : Execute WM Material Staging for Production Orders

List of BAPI for Process Order

BAPI_PROCORDCONF_CANCEL		Cancel Process Order Confirmation
BAPI_PROCORDCONF_CREATE_ACT		Enter Activity Confirmations for Process Orders
BAPI_PROCORDCONF_CREATE_HDR		Enter Confirmations for Process Order Header
BAPI_PROCORDCONF_CREATE_TE		Enter Confirmation Time Event for Process Order
BAPI_PROCORDCONF_CREATE_TT		Enter Confirmation Time Ticket for Process Order
BAPI_PROCORDCONF_EXIST_CHK		Existence Check for Confirmation of Process Order
BAPI_PROCORDCONF_GETDETAIL		Detail Data for Process Order Confirmation
BAPI_PROCORDCONF_GETLIST		List of Confirmations for Process Orders
BAPI_PROCORDCONF_GET_HDR_PROP		Propose Data for Confirmation of Process Order
BAPI_PROCORDCONF_GET_TE_PROP		Propose Data for Confirmation Time Event Process Order
BAPI_PROCORDCONF_GET_TT_PROP		Propose Data for Process Order Confirmation Time Ticket
BAPI_PROCORD_CHANGE		BAPI: Change Process Order
BAPI_PROCORD_CHECK_MAT_AVAIL		BAPI: Execute Material Availability Check for Process Orders
BAPI_PROCORD_CLOSE		BAPI: Close Process Orders
BAPI_PROCORD_COMPLETE_TECH		BAPI: Technically Complete Process Orders
BAPI_PROCORD_COSTING		BAPI: Carry Out Costing for Process Orders
BAPI_PROCORD_CREATE		BAPI: Generate Process Order
BAPI_PROCORD_CREATE_CAP_REQ		BAPI: Create Capacity Requirements for Process Orders
BAPI_PROCORD_CREATE_FROM_PLORD		BAPI: Convert Planned Order into Process Order
BAPI_PROCORD_CREATE_FROM_REF		BAPI: Create Process Order with Reference Order
BAPI_PROCORD_EXIST_CHECK		BAPI: Check Existence of a Process Order
BAPI_PROCORD_GET_DETAIL		BAPI: Output Details of a Process Order
BAPI_PROCORD_GET_LIST		BAPI: Output Process Order Header Data in a List
BAPI_PROCORD_RELEASE		BAPI: Release Process Orders
BAPI_PROCORD_REVOKEUSERSTATUS		BAPI: Reset User Status for Process Orders at Header Level
BAPI_PROCORD_SCHEDULE		BAPI: Schedule Process Orders
BAPI_PROCORD_SETUSERSTATUS		BAPI: Set User Status for Process Orders at Header Level
BAPI_PROCORD_SET_DELETION_FLAG		BAPI: Set Deletion Flag for Process Orders
BAPI_PROCORD_SET_DEL_INDICATOR		BAPI: Set Deletion Indicator for Process Orders
BAPI_PROCORD_WM_MAT_STAGING		BAPI: Execute WM Material Staging for Process Orders

3)  Depend on the requirement we will use following BAPI’s in MII for Production order

BAPI_PRODORD_CREATE - create production orders

BAPI_PRODORD_RELEASE - release production orders

BAPI_PRODORD_GET_LIST - list production orders

BAPI_PRODORD_GET_DETAIL - get production orders details

BAPI_PRODORDCONF_CREATE_TT - does the quantity/time (time ticket) confirmation

BAPI_GOODSMVT_CREATE - generates the goods receipt

And for Process order Below BAPI’s May use

BAPI_PROCORD_CREATE - create process orders

BAPI_PROCORD_RELEASE - release process orders

BAPI_PROCORD_GET_LIST - list process orders

BAPI_PROCORD_GET_DETAIL - get process orders details

BAPI_PROCORDCONF_CREATE_TT - does the quantity/time (time ticket) confirmation

4) There is no specific  life cycle in ECC – MII , its all depends on your requirement  …

Typical Life Cycle includes : 1) First Connectivity Between MII and ECC

                                                 2) Calling BAPI using SAP JCo Interface Action Block in BLS Transaction

                                                 3)Develop UI for the Users

Ex: If you want to create a production order in ECC using MII, First need to develop a BLS transaction by calling   “BAPI_PRODORD_CREATE” using SAP JCo Interface Action block and follow necessary steps. Develop a UI for the End Users through which they may create / confirm the production order / process order .

Regards

Muthu

[SS15 · Accepted solution]

Thanks Muthu,

This is indeed a excellent summary on both.

We completed one way scenario using the BAPI - procord_get_details to read data from ecc to mii and share with MES.

My SAP team however couldnt get find BAPI for reversal scenario - MII to ECC.

To update the confirmed quantity in ECC,which MII has read from MES.

Can you share bapi to update this detail into ECC.also field mapping

like AUFNR - Process Order number

IFTNR - start date and also on....

so that i can mapped exact field data in MII corresponding to BAPI to update/and reflect the change in ECC SAP fields.

Again,thanks a ton for ur detailed reply

[muthulingaiah · Accepted solution]

Hi Shailaja,

        For Posting details from MII(from MES) to SAP we will use different BAPI's ...

E.g: For Order Confirmation we will use BAPI's like BAPI_PROCORDCONF_CREATE_TT for Process order Confirmation and BAPI_PRODORDCONF_CREATE_TT for Production Order Conformation .

I think in your scenario requirement is for order confirmation , so you can use either BAPI_PROCORDCONF_CREATE_TT or BAPI_PRODORDCONF_CREATE_TT based on your requirement .

For Field Mapping in BAPI's , you can find all the description of BAP's fields in ECC with T-code of SE37 or SE80, how ever please find the field mapping details below ...

Available Input Table Stricture in BAPI BAPI_PROCORDCONF_CREATE_TT:

In this BAPI we have to map input fields(from MES) to GOODSMOVEMENTS structure under the BAPI, fields Available in GOODSMOVEMENTS structure is like below ... for Each field has its own description which is very easy to understand and map the suitable input field to this fields  ... The Description of fields is like below ...

Material: Material NUmber, Plant: Plant Number , Stg_Loc: Storage Location, Batch: Batch Number, Move_Type: Movement Type, Stck_Type:Stock Type, Spec_Stock:Specification/Special Stock, Vendor: Vendor Name, Customer: Customer Name, Sales_ord: Sales Order Number, S_Ord_Item: Sales Order Item, Sched_Type: Schedule Type, Val_Type:Value Type, Entry_Qntry:Entry Quanity, Entry_UOM: Entry Unit of Measurement, Entry_UOM_ISO: Entry Unit of Measurement as Per ISO, PO_PR_QNT: Process Order Print Quantity, ORDERPR_UN: Order Price Unit, ORDERPR_UN_ISO: Order Price Unit as per ISO etc ... like wise for other fields description you can find it easily by comparing fields in MES with fields in ECC ....

Here you can found more than or near 50 fields in GOODSMOVEMENT structure map the desired fields in MES with GOODSMOVEMENT fields ... after thsi you have to map some more fields in another structure like below ... LINK_CONF_GOODSMOV

Like wise for BAPI_PRODORDCONF_CREATE_TT BAPI also need to follow the same steps ...

I hope this information will help you developing your scenario ...if you need any information let me know ...

Regards

Muthu

[SS15 · Accepted solution]

Thank you for the response, Muthu

Regards,

Shail

[adnanmaqbool · Accepted solution]

Hi Muthu

Old post , but needs clarification on your last point.

Why should we use BLS Transaction within MII to transfer a Production Order or Confirmation in ERP. We can easily provide the SAP ERP access/user id on Plant to enter production order details directly in ERP, what benefit we are getting on creating another layer to duplicate same functionality which ERP is already having.