Use report RPCO_BS_INT_TEST
Dest RFC = PCO_LA_RINCONADA
Untick « Test mode »
tags are in « Tag Providers » – « Default ».
PCO & Ignition interfaces
Répondre
Archives de catégorie : PP
BAPI PP
https://blogs.sap.com/2013/07/12/list-of-bapi-for-production-planning-module/
About BAPI:
BAPIs enable access to SAP functions across formal, stable and dialog-free interfaces. These interfaces can be used by external applications developed by customers and complementary software partners as well as by other SAP applications. Defined as API methods of SAP Business Object Types, these object types are used within the Business Framework to enable object-based communication between components.
Business objects and their BAPIs enable object orientation to be used in central information processing in companies. For example, existing functions and data can be re-used, trouble-free technical interoperability can be achieved and non-SAP components can be implemented. Applications can use BAPIs to directly access the application layer of the R/3 System and, as clients; applications can use the business logic of the R/3 System. BAPIs provide the client with an object-oriented view of the application objects without needing to know the implementation details. BAPIs are always developed by defining scenarios which are used to map and implement system-wide business processes.
LIST OF BAPI FOR PRODUCTION PLANNING :
Routing:
BAPI_ROUTING_CREATE Creation of a routing
BAPI_ROUTING_EXISTENCE_CHECK Check existence of object
Reference operation set:
BAPI_REFSETOFOPERATIONS_CREATE Creation of a reference operation set
BAPI_REFSETOFOPR_EXISTENCE_CHK Check existence of reference operation set
Planned order:
BAPI_PLANNEDORDER_CHANGE Change Planned Order
BAPI_PLANNEDORDER_CREATE Create Planned Order
BAPI_PLANNEDORDER_DELETE Delete Planned Order
BAPI_PLANNEDORDER_EXIST_CHECK Check Existence of Object
BAPI_PLANNEDORDER_GET_DETAIL Get Details for Planned Order
BAPI_PLANNEDORDER_GET_DET_LIST Get Detailed List
Planned Independent Requirement:
BAPI_REQUIREMENTS_CHANGE Change Planned Independent Requirement
BAPI_REQUIREMENTS_CREATE Create Planned Independent Requirement
BAPI_REQUIREMENTS_GETDETAIL Display detail of P.I.R
Production order:
BAPI_PRODORD_WM_MAT_STAGING WM Material Staging
BAPI_PRODORD_SETUSERSTATUS Set User Status
BAPI_PRODORD_SET_DEL_INDICATOR Set Deletion Indicator
BAPI_PRODORD_SET_DELETION_FLAG Set Deletion Indicator
BAPI_PRODORD_SCHEDULE Carry Out Scheduling
BAPI_PRODORD_REVOKEUSERSTATUS Cancel User Status
BAPI_PRODORD_RELEASE Release
BAPI_PRODORD_GET_LIST List of Order Headers
BAPI_PRODORD_GET_DETAIL Order Detail Data
BAPI_PRODORD_EXIST_CHECK Existence Check
BAPI_PRODORD_CREATE_FROM_REF Create with Template
BAPI_PRODORD_CREATE_FROM_PLORD Create with Planned Order
BAPI_PRODORD_CREATE_CAP_REQ Generate Capacity Requirement
BAPI_PRODORD_CREATE Create Production Order
BAPI_PRODORD_COSTING Create Cost Estimate
BAPI_PRODORD_COMPLETE_TECH Complete Technically
BAPI_PRODORD_CLOSE Close Order
BAPI_PRODORD_CHECK_MAT_AVAIL Check Material Availability
BAPI_PRODORD_CHANGE Change Production Order
Production order confirmation:
BAPI_PRODORDCONF_GET_TT_PROP Propose data for time ticket confirmation
BAPI_PRODORDCONF_GET_TE_PROP Propose data for time event confirmation
BAPI_PRODORDCONF_GETLIST Confirmation lists
BAPI_PRODORDCONF_GETDETAIL Detailed data for production order confirmation
BAPI_PRODORDCONF_GET_HDR_PROP Propose data for order confirmation
BAPI_PRODORDCONF_EXIST_CHK Check existence of object
BAPI_PRODORDCONF_CREATE_TT Enter time ticket confirmation
BAPI_PRODORDCONF_CREATE_TE Enter time ticket confirmation
BAPI_PRODORDCONF_PDC_UPLOAD_TT Transfer time ticket confirmations from PDC system
BAPI_PRODORDCONF_PDC_UPLOAD_TE Transfer time ticket confirmations from PDC system
BAPI_PRODORDCONF_CREATE_HDR Enter order confirmations
BAPI_PRODORDCONF_CREATE_ACT Enter activity confirmation
BAPI_PRODORDCONF_CANCEL Cancel production order confirmation
BDC Download & Upload for production order:
BAPI_RCVPRORDCF_RECEIVEPRODORD PP-PDC: Download production orders
BAPI_RCVPRORDCF_RECEIVEWORKC PP-PDC: Download work centers
BAPI_RCVPRODCF_REQUEST_CONF PP-PDC: Upload request
KANBAN:
BAPI_KANBAN_CHANGE Change Kanban Data
BAPI_KANBAN_CHANGESTATUS Change status of a kanban
BAPI_KANBAN_CHANGESTATUS1 Change status of a kanban
BAPI_KANBAN_GETLIST Determination of Kanbans Matching Selection Criteria
BAPI_KANBAN_GETLIST_ALL Determination of Kanbans Matching Selection Criteria
BAPI_KANBAN_GETLISTFORSUPPLIE1 Determination of Kanbans Matching Selection Criteria
BAPI_KANBAN_GETLISTFORSUPPLIER Provide Kanban data for vendors
BAPI_KANBAN_SETINPROCESS Provide Kanban data for vendors
KANBAN CONTROL CYCLE:
BAPI_KANBANCC_ADDEVENTDRKANBAN Create Event-Driven KANBAN for Control Cycle
BAPI_KANBANCC_CHANGE Change Control Cycle
BAPI_KANBANCC_CREATE Create Control Cycle
BAPI_KANBANCC_DELETE Delete Control Cycles
BAPI_KANBANCC_EXISTCHECK Check Existence of Control Cycle
BAPI_KANBANCC_GETLIST Determine Kanban Control Cycles with Selection Criteria
BAPI_KANBANCC_GETLIST_ALL Determine Kanban Control Cycles with Selection Criteria
BAPI_KANBANCC_WITHDRAWQUANTITY Quantity Signal for Kanban Control Cycle
REM Confirmation:
BAPI_REPMANCONF_CANCEL Reverse REM Backflush
BAPI_REPMANCONF_CREATE_MTO Execute Backflush in Sales Order Scenario
BAPI_REPMANCONF_CREATE_PLOT Execute Backflush in Production Lot Scenario
BAPI_REPMANCONF_CREATE_MTS Execute Backflush in Production Lot Scenario
BAPI_REPMANCONF_EXIST_CHK Check Existence of Object
REM Confirmation1:
BAPI_REPMANCONF1_CANCEL Reverse REM Backflush
BAPI_REPMANCONF1_CREATE_MTO Execute Backflush in Sales Order Scenario
BAPI_REPMANCONF1_CREATE_MTP Execute Backflush in Production Lot Scenario
BAPI_REPMANCONF1_CREATE_MTS Execute Backflush in Stock Scenario
BAPI_REPMANCONF1_EXIST_CHK Check Existence of Object
Process order PI:
BAPI_PROCORD_WM_MAT_STAGING WM Material Staging
BAPI_PROCORD_SETUSERSTATUS Set User Status
BAPI_PROCORD_SET_DEL_INDICATOR Set Deletion Indicator
BAPI_PROCORD_SET_DELETION_FLAG Set Deletion Indicator
BAPI_PROCORD_SCHEDULE Carry Out Scheduling
BAPI_PROCORD_REVOKEUSERSTATUS Cancel User Status
BAPI_PROCORD_RELEASE Release
BAPI_PROCORD_GET_LIST List of Order Headers
BAPI_PROCORD_GET_DETAIL List of Order Headers
BAPI_PROCORD_EXIST_CHECK Existence Check
BAPI_PROCORD_CREATE_FROM_REF Create with Template
BAPI_PROCORD_CREATE_FROM_PLORD Create with Planned Order
BAPI_PROCORD_CREATE_CAP_REQ Generate Capacity Requirement
BAPI_PROCORD_CREATE Create Process Order
BAPI_PROCORD_COSTING Create Cost Estimate
BAPI_PROCORD_COMPLETE_TECH Complete Technically
BAPI_PROCORD_CLOSE Close Order
BAPI_PROCORD_CHECK_MAT_AVAIL Check Material Availability
BAPI_PROCORD_CHANGE Change Process Order
Process Order Confirmation:
BAPI_PROCORDCONF_CANCEL Cancel Process Order Confirmation
BAPI_PROCORDCONF_CREATE_ACT Enter Activity Confirmation
BAPI_PROCORDCONF_CREATE_HDR Enter Order Confirmations
BAPI_PROCORDCONF_CREATE_TE Enter Confirmation Time Events
BAPI_PROCORDCONF_CREATE_TT Enter Time Ticket Confirmation
BAPI_PROCORDCONF_EXIST_CHK Check Existence of Object
BAPI_PROCORDCONF_GET_HDR_PROP Propose Data for Order Confirmation
BAPI_PROCORDCONF_GETDETAIL Detail Data for Process Order Confirmation
BAPI_PROCORDCONF_GETLIST List of Confirmations for Process Orders
BAPI_PROCORDCONF_GET_TE_PROP Propose Data for Time Event Confirmation
BAPI_PROCORDCONF_GET_TT_PROP Propose Data for Time Ticket Confirmation
Process Characteristic PI:
BAPI_PROC_CHAR_GET_HELPVALUES Get Allowed Values for Process Characteristic
BAPI_PROC_CHAR_GET_LIST Read Characteristic List Incl. Details
Process Message PI:
BAPI_PROCESS_MESSAGE_CREATEMLT Create process messages
BAPI_PROCESS_MESSAGE_CHK_EXIST Check process message existence
Control Recipe:
BAPI_CONTROL_RECIPE_GET_LIST Read control recipe list
BAPI_CONTROL_RECIPE_REQUEST Request and transfer control recipes
RCCYMAB1 and RCCYMAB1 for auto loading orders
Schedule a mass loading of what’s appearing on CM25.
RCCYMAB1 to create the parameters.
RCCYMAB2 to schedule the run.
BAPI BAPI_MATERIAL_MRP_LIST type of objects
WB – Starting stock
PA – Planned order
BR – Process order
PP – Independant Requirements
VC – Customer order
VJ – Outbound Delivery
LA – Inbound Delivery
LE – Schedule line
UR – Inbound Transfer reservations
MR – Material Reservation (Outbound)
U1 – Outgoing STO
U2 – Outgoing STR
SB – Dependant Requirements
AR – Order reservation
BB – Subcontracting Requirements
BA – Purchase Requisitions
BE – Purchase Order
Frequent Issues on MD04
From https://archive.sap.com/documents/docs/DOC-49467
Frequent issues on MD04
The most used transaction in PP-MRP is the stock/requirements list.
Issues from many different application areas are reflected in transaction MD04, since this transactio reads data from many different tables.
On this document you will find the most frequent issues observed on transaction MD04.
1 – An MRP element is displayed on transaction MD04, however, it does not affect the available quantity, that means, it is not MRP relevant.
This issue can happen for many different planning elements, from sales orders to dependent requirements and there are many different causes for this issue.
On the following note you will find a detailed explanation for the possible causes for each different planning element:
1825187 – MD04/MD05: Incorrect quantity for an MRP element
2 – Database inconsistencies
A planning element that is already completed is still displayed on MD04 or a planning element is incorrectly displayed on MD04. It generally happens for sales orders or for subcontracting requirements but it can also happen for another planning elements, such as dependent requirements. The following WIKI describes each inconsistency and how to correct it:
3 – Exception messages
There are usually several questions related to exception messages, for example, why an exception message appears on MD05 but not on MD04. The answer to this and another questions can be found on the following note:
550441 FAQ: Exception messages in material requirements planning
From all the exception messages, those related to the rescheduling check are the most frequent cause of issues. There is a lot of documentation about rescheduling and the following WIKIs and notes should be useful:
550302 FAQ: Rescheduling check
1745312 MRP creates redundant proposals though there are fixed future receipts which can cover the requirements.
http://wiki.scn.sap.com/wiki/display/ERPMan/What+is+rescheduling+and+how+does+it+work
4 – Why a planning element is displayed on MD04?
The following WIKI explains how to analyze MD04 in debug and find out where a planning element is comming from and why it is displayed on MD04:
http://wiki.scn.sap.com/wiki/display/ERPMan/How+to+analyze+the+MRP+elements+by+debugging
5 – Issues related to sales orders:
See the following document:
MD04: Problems with sales orders
Tags: md04mrp_listsap_erp_logistics_materials_managementmaterial_planningppmrpsap_erp_manufacturing_production_planningerpproductionorderplannedproduction_schedulingplanned_ordersproduction_orderplanningstock_requirements_listenterprise_resource_planningmaterial_managementmd05
Transporter des variantes
SE38, report RSTRANSP
Pull List and Stock Determination in Production
Pull List and Stock Determination in Production – MF60
https://blogs.sap.com/2015/02/25/pull-list-and-stock-determination-in-production/
1. Pull List
The pull list controls the in-house flow of material for supplying production with materials. The system assumes that the components required for production have already been produced in-house or procured externally and are now available to be transferred from their current storage location or bin to the production storage location.
The pull list checks the stock situation at the production storage location and calculates the quantities of missing parts. Replenishment elements can be created for these missing parts.
2. Master Data
Here we are going to review the key master data needed to use the Pull List.
2.1. Production Storage Location
Issue location for production order
Number of the issue location from which the material is issued during the production process. Backflush is posted to this issue location if required.
Use
In production, this is the access sequence in which the determination of the production storage location occurs:
- First, the issue storage location of the material to be issued (MARC-LGPRO) is transferred to the material master from the MRP data if it is
filled. - The system overwrites this value with the issue storage location from the bill of material (RC29P-LGORT, STPO-LGORT) if it is filled.
- If the operation to which the component is assigned in production order contains a work center with supply area, the storage location is transferred
from this supply area (PVBE-LGORT). However, this transfer is only carried out if storage location data (MARD) is maintained for this storage location for the material.
Ref.: OSS Note: 137225 – Prod. order: Issuing storage location for component
Depending on if your component is used in more than one production storage location, you could asisgn this in the material master or in the BOM or through a Supply Area. Let’s supose in this example that we assign this at BOM item level.
This is maintained using t-code CS02. The production storage location is assigned at item level. Once you are in the BOM, click twice on each BOM item and go to Status/Lng Text tab:
2.2. Stock determination
The pull list controls the in-house flow of material for supplying production with materials. The system assumes that the components required for production have already been produced in-house or procured externally and are now available to be transferred from their current storage location or bin to the production storage location.
This automatic transfer between the current storage location to the production storage location is performed based on the stock determination strategy.
Strategies for Stock Determination
You make all the settings you require for a stock determination strategy.
You determine a strategy at plant level using the stock determination group and the stock determination rule (The terms ‘rule’ and ‘group’ correspond to the checking group and the checking rule logic in the availability check).
The customizing point for the Strategies for Stock Determination is:
SPRO –> Materials Management –> Inventory Management and Physical Inventory –> Stock Determination –> Define Strategies for Stock Determination
The stock determination group is assigned to the material in the material master record.
3. Pull List Execution
Suppose your business is running the following process:
- Create and Schedule process orders: the planner creates the process orders and the production scheduler schedules all the process orders.
- Material staging: warehouse responsible will receive the list of process orders and will move components to the shop floor based on: which is the material that will be produced and which is the production line capacity.
- Production execution: production responsible executes the production of the corresponding process order.
- Goods receipt & confirmation: finished good production quantity is received and the confirmation is done. At this moment components are consumed from the production storage location using Backflush.
3.1. Create and Schedule process orders
Let’s create a process order and ensure the Production Storage Location is determined as expected.
Take a look of the component list. All the components have an assigned production storage location:
3.2. Material staging (MF60: Pull List)
The warehouse responsible will move components to the shop floor (production storage location). This can be done based on process order number or entering the material and quantity to be produced (this is commonly used when the order takes several days and we only want to supply components on a daily basis for the corresponding production of the day)
In this example suppose that the first process order is: 304472 and its duration is 5 days. The corresponding finished good is: 403403 (production version: 0001) and the production line maximum capacity is 5000CS/day.
Material Staging is executed thru transaction: MF60.
The pull list checks the stock situation at the production storage location and calculates the quantities of missing parts. Replenishment elements can be created for these missing parts (this is the section at the bottom of the screen).
Let’s see what is each column:
- Issue stor. location = production storage location. This was entered in the bill of material.
- NetReqQty = component quantity based on maximum production line capacity. In case the Pull list is executed agains an order, here you will see the quantity of the component determined in the order.
- Available stock = this is the available stock in the issue storage location (production storage location). This can be the available remaining quantity of the before production day or shift or order.
- Quantity staged = NetReqQty – Avail.Stock = This is the remaining quantity to be moved to the shop floor (production storage location).
- RepLoc = is the warehouse storage location. It is the location found by the stock determination strategy.
Finally.. you press Save and the components will be moved from the main warehouse to the production storage location
4. Pull List Global Settings
If necessary, limit your selection using the Global settings . Here, you have the choice between:
- General settings
For example, you may choose to display components with missing quantities only in the pull list or, using the indicator Take all requirements into account , you may define that the system is to include the requirements of all orders that influence the missing parts situation. If this field is not selected, the system only includes requirements for the specific order that you entered in the missing parts calculation. Here, you can also define whether your components are staged at storage location level via direct stock transfer, or using stock transfer reservation.
- Settings for dialog control
Here, you define which procedures are to be carried out automatically in the pull list and which are to be carried out in dialog mode.
You also define whether the system is to save a complete log of all the messages and whether this log is to be displayed automatically.
- Printing settings
Here, you make the settings for the print list.
References:
Pull List – Repetitive Manufacturing (PP-REM) – SAP Library
Accessing the Pull List – Repetitive Manufacturing (PP-REM) – SAP Library
OSS Note: 137225 – Prod. order: Issuing storage location for component
Alternative resources through caracteristics
https://blogs.sap.com/2013/07/03/resource-classification-in-master-recipe-for-planning/
Workcenter, PDS, ressources, alternatives.
Often, many industries like FMGC, chemical, pharmaceutical, etc use multiple similar resources to manufacture a product.
E.g. A plant has many mfg bagger, or filling lines with identical capacities. A product is chronologically said to be manufactured in bagger 2. Alternatively this product also can be manufactured in bagger 3 or bagger 4 if needed. On shop-floor business cannot determine the primary resource to be used until shortly before order processing. But in mid to long term planning, they want to assign a suitable planning resource to the operations provisionally.
The constraint for long term planning needs to be on planning resource. In short term the flexibility needs to be given for resource selection based on SKU. This can be mapped in different ways in SAP.
1. By multiple production Versions with multiple master recipe
This method is most widely used but requires laborious master data maitainance as one recipe has to be created explicitly for each resource and has to be assigned to one production version respectively.
2. By manual selection in the Order.
The resource is changed manually on the Order. This change requires a single approval process if ECM to be used. Production Planners will feel as more work and any change which needs a Quality Approval in GMP environments will take more time to create and release the order for production.
3. By Resource Selection through classification.
SAP provides another way of maintaining this alternate resource selection by using resource classification.
We can use a planning resource as the primary resource and select the alternate resource through the resource network maintained through work center classification (type 019). This also works well with ECM and is a good option for Planners as there is no need of Single Approval from QA personnel.
Create a Characteristic (T-Code CT04)
We can create classifications in ECC for suboperations and secondary resources.
In Additional data tap define Table Name as CRHD and Field Name as ARBPL.
Create Class and assign characteristics to class T Code: CL02
Assign classification in ressource T Code: CRC1 or CRC2
All relevant alternative work centers must contain exactly the same classification and characteristic value assignment. Work centers with different classes or characteristic values are ignored.
Assign the classification in master recipe and add alternate resources T Code: C201 or C202
Create process order COR1 or By MRP Planned order to Process order
On the operations tab, select the operation 10 and click on Resource selection condition
Product can be produced on all 3 lines here you can select the resource accordingly.
Capacity Planning CM25
We can change the resource from this screen by dragging and dropping it to another resource from the resource section.
Resource classification automatically creates multiple modes in APO PDS or PPM, so it can be used in PPDS while converting SNP Plan orders to PPDS plan orders. And in DS board we can schedule the order on required resource.
If we want to use different capacities for planning, but for execution purpose we only want to use one resource. So from many lines in mid term planning to accommodate constraints, but for short term we use single resource for production execution.
Mass TSUP on process order : COAC
SAP IDOC LOIPRO missing the workcenter segment
Workcenter segment ARBID is generated only on scheduled orders.
You need to either manualy schedule the order (COR2) or activated in the production scheduler profile the automatic scheduling at release.