In subcontracting process, the subcontractor/vendor will be provided with materials (components), which he consumes to produce the finished product.

We have to create MRP area for each subcontractor, If we want to plan provision of components for individual subcontractors separately from the usual requirements.

In this blog we will be discussing about the below mentioned scenarios,

• Stock Transfer of Components to be Provided for subcontracting.
  
• Third-Party Order Processing for subcontracting.

Stock Transfer of Components

In this case, We will procure the components that are required for subcontracting from a vendor Z and then transfer the stock from the plant storage location to the MRP area of the subcontractor X.

Third-Party Order Processing

In this case, the components to be provided for a subcontractor is procured externally from the vendor Z and then it is delivered directly to the MRP area of the subcontractor X.

Scenario

We will be issuing the component RM material BW-R1003SC and BW-R1004SC to the subcontractor to produce the SFG material BW-S1001SC.

We will perform the Stock Transfer process for the Component RM BW-R1003SC and will perform the Third-Party Order Processing for the component RM BW-R1004SC.

Prerequisite Master Data Setup

• Bill Of material

Using Transaction code CS01 – Create Subcontracting Bill Of material for the SFG Material BW-S1001SC.

• Production version

Using Transaction code MM01 – Assign the Production Version with the Subcontracting BOM to the SFG Material BW-S1001SC

• Material Master – MRP Area and Special Procurement Key assignment

Maintain the special procurement key Subcontracting 30 for the SFG Material BW-S1001SC

For the component material R1003SC. Assign the Subcontracting MRP Area and maintain the Special procurement as Z4 , If Stock Transfer of Components to be Provided to the subcontractor.

In Customizing – Special procurement key Z4 is created for Stock transfer from plant to MRP area.

• Procurement type : F for External procurement
  
• Special procurement: U for Stock transfer
  
• Plant: Number of plant 1710 , to which the MRP area belongs.

For the component material R1004SC, Assign the Subcontracting MRP Area and maintain the Special procurement as 20, If the component material is externally procured with delivery directly to the subcontractor .

• Purchasing Info Record

For the SFG Material we should have a valid subcontracting purchasing info record with automatic sourcing indicator.

And for the component RM materials, we should have the standard purchasing info record with automatic sourcing indicator.

Process Flow

• Maintain the Forecast / Demand as Planned Independent requirement.

In Transaction code MD61 maintain the PIR for the SFG material BW-S1001SC at plant level.

In Transaction code MD04 , Stock Requirement List is displayed.

SFG Material

RM Material

• Material Requirement Planning

In Transaction code MD01N, MRP Live is executed.

In Transaction code MD04, Stock Requirement List is displayed.

For the SFG material BW-S1001SC Subcontracting Purchase Requisition 0010093462 is created.

For the RM material BW-R1003SC

Material Reservation 0000100166 is created for subcontracting (541 Movement type – Goods issue to subcontractor) and a Purchase requisition 0010093464 is created as we don’t have enough stock at Plant MRP Area level.

Transfer requisition 0000100166 (With respect to Material reservation) and subcontractor requirements for the purchase requisition 0010093462 are created at the subcontractor MRP Area level.

For the RM material BW-R1004SC

No MRP element is created at Plant MRP Area level.

Purchase requisition 0010093463 is created as we don’t have enough stock and subcontractor requirements for the purchase requisition 0010093462 are created at the subcontractor MRP Area level.

• Procurement of Component Raw material

For the RM material BW-R1003SC PR 0010093464 is converted to PO 4500491341 and GR at plant / storage location is posted.

For the RM material BW-R1004SC PR 0010093463 is converted to PO 4500491342 and GR at subcontracting vendor location is posted.

• Processing of Subcontracting Order

For the SFG material BW-S1001SC , The Subcontracting Purchase Requisition 0010093462 is converted to Subcontracting Purchase order 4500491343 using the transaction code ME21N.

In Transaction code ME2O, the component material are issued to the subcontractor.

For the component RM material BW-R1003SC, the subcontracting stock is Zero.

For the component RM material BW-R1004SC ,We have already received the stock directly in supplier location. So the subcontracting stock is 100.

For the component RM material BW-R1003SC, the required quantity is posted to the subcontracting vendor location after stock transfer.

Both the component RM materials BW-R1003SC and BW-R1004SC has the required stock in the Subcontractor Location.

In the transaction code MIGO, Perform Goods receipt against the subcontracting purchase order is performed.

In the transaction code MD04 – Stock Requirement List, the forecasted quantity is procured by subcontracting process.

The post S/4HANA Planning for Components to be Provided in Subcontracting Process appeared first on ERP Q&A.

Are you bored of running capacity planning in addition to running the MRP live. Here is the way to avoid it by using the SAP PPDS which is now included in S/4 HANA itself. (Since 2016)

System Architecture:

Previously PPDS was with APO system which is separate from ECC

(Like how we are logging in to DEV and QAS system separately)

APO system will have separate credentials and ECC will have separate credentials.

ECC now S/4 HANA – consider it as a execution system. PP Master data will be stored here and moved to APO system via CIF for planning.

APO PPDS now embedded in S/4 HANA. – Once it got the data from ECC it will do the planning by considering the capacity, relationships between phases, queue time, inter operations time and create a temporary transactional data with temporary number range and move it to ECC.

In ECC the temporary transactional data (Planned order, Process order, Purchase requisition..) will be created as actual transactional data with actual number ranges and again will be transferred back to APO system to capture the actual number range in APO. later the confirmation, consumption will takes place in ECC.

Simply we will say sap APO as planning system and ECC as execution system. Now the PPDS is available in ECC itself and not like a addon.

Actually APO consist of DP, SNP, PPDS, GATP. Out of which only PPDS is embedded to S/4 HANA

Disadvantage of SAP PP is infinite scheduling.

Advantage of PPDS is finite scheduling and it will be achieved at Planning run (like MD01N) itself.

Finite scheduling – MRP will consider the capacity. (Lathe Machine – it can work only up to a extend a day, So we need to consider the capacity and to create the order accordingly)

Infinite scheduling – MRP will not consider the capacity. (Cooling tower – In thermal power plant the steam need to be cooled after using it. The cooling tower will not have any capacity. It will work infinitely without any capacity bottlenecks)

In this blog I will explain how to avoid the capacity planning and how to do finite scheduling via PPDS on running production planning run.

Main Part:

Master data in PPDS will be said as below. It will be displayed with separate tcode.

Product – /n/SAPAPO/MAT1

Resource – /SAPAPO/RES01

Location – /SAPAPO/LOC3

PDS – /SAPAPO/CURTO_SIMU – Note * always use /n in front of APO transaction

But the Master data creation for PPDS is same as like SAP PP module except some additional fields shown below.

Activating the advance planning checkbox in Material master and work center will create/transfer the data for PPDS.

Material Master – MM01

Highlighted fields to me maintained

Work Center – CR01

If you activate the advance planning all the changes in master data will be moved to PPDS Master data except production version, Which you need to move manually to PPDS after every change via CURTOADV_CREATE

Here PPDS activation and master data is clearly explained

Location – Plant and storage location you have to create extra in PPDS via transaction /SAPAPO/LOC3

Scenario:

I have created master data in PP as below

FG20 – BOM SFG20 1 EA – One Operation – Assembly FG20 (1 per day as per Work center capacity)

SFG20 – BOM – RAW20 1 EA – One Operation – Assembly SFG20 (1 per day as per Work center Capacity)

RAW20

After creating the master data I have moved the PDS via CURTOADV_CREATE

BOM

Work Center Capacity – Should have finite scheduling – Same for SFG20

Routing – Same for SFG20

PIR

1st requirement for FG at 04.09.2023 – 5 EA

2nd requirement for FG at 05.09.2023 – 5 EA

Strategy 40

Backward scheduling

Calendar for reference – consider the week ends.

Running PPDS MRP – Production Planning Run

Now Running the PPDS MRP – Production Planning Run /SAPAPO/CDPSB0

While running it we need to use multiple Heuristics to achieve our destiny

Heuristic 1 : Stage-Numbering Algorithm for PP/DS – for getting the multilevel BOM

Heuristic 2: Product Planning (Comp. acc. LLevl Code) – To run the MRP as like MD01N

Heuristic 3: Enhanced Backward Scheduling – To do the detailed scheduling.

You can add multiple heuristics on steps displayed in the same screen.

After executing the Production planning run we will see the results in product view – /SAPAPO/RRP3 as like MD04 in HANA

Here you can see the date of availability of order has been scheduled accordingly.

Now we will see the same in Detailed scheduling board – /SAPAPO/CDPS0 like CM25 or capacity scheduling board in HANA.

1st sfg order starting on 15.08.2023

2nd sfg order starting on 22.08.2023

1st FG order starting on 22.08.2023

2nd FG order starting on 29.08.2023

We will see the same in COOIS.

See the basic start date of planned order. We reached our expectation of finite scheduling in PPDS MRP itself without capacity leveling.

If I run MD01N I am getting bellow results. Need to do capacity scheduling seperaterly.

In Monitor Capacity utilization app we could able to see that there are no over loads.

Not sure i am not able to see the data in capacity scheduling board.

The post PP/DS Step by Step Guide – Functional PP Process- Detailed scheduling in PPDS appeared first on ERP Q&A.

To guarantee seamless operations in SAP Plant Maintenance (PM), effective work order management is essential. SAP PM provides the idea of a User Status Profile to speed up the process and enforce control over order release. We will delve into the definition of User Status Profile, its importance in limiting order release, and how it may be set up in SAP PM in this blog post.

Understanding User Status Profile:

In SAP PM, the user-definable User Status Profile is a framework that enables you to define and assign user statuses to work orders. A work order’s lifecycle stage or condition are represented by a user status. It can be used to manage different system processes and workflows and serves as a flag indicating the status or progress of an order.

Benefits of User Status Profile:

There are many advantages to implementing a User Status Profile in SAP PM, including:

• Improved order control: The User Status Profile feature enables you to impose a formal approval procedure and manage the release of work orders.
  
• Efficiency gain: By establishing specified conditions, you can make sure that orders comply with particular requirements before being distributed, reducing errors and rework.
  
• Improved compliance: User Status Profile makes sure that orders follow specified checks and approvals, which aids organizations in meeting regulatory standards.
  
• Workflow transparency: Orders with designated user statuses have insight into the status and progress of each order, allowing for more efficient monitoring and decision-making.

Configuration User Status Profile:

Goto SPRO > Plant Maintenance and Customer Service > Maintenance and Service Processing > General Data > User Status for Orders > Define Status Profile > Define User Status Profile for Orders

Or you can use T-code BS02

Here Create a User Status Profile with an object Maintenance Order

Here

The status order number is used to define the sequence of the user statuses in a status profile.

Status is Key which informs you of the current status of an object.

Init. status If status is marked as an initial status, it is automatically activated in an object when the object is created.

The system records the highest status number reached so far, and the “lowest number” within that range determines the number for a new status.

Auth. code You provide each of those user statuses an authorization key if you want to guarantee that only members of a specific group can change a particular user’s status.

now check the details for each status

Now after creating User Status profile assign this to the Order type.

After these configuration settings now create a maintenance order.

Currently, it is not possible to change the system status for the order because the required approval is missing. as here in the screen.

Once all necessary information has been inputted in the maintenance order, save and submit the order for approval. The approving user must possess the authorization code as in our example PM_APPR.

now approving user set status APPR -Release Approve after verifying all information.

Conclusion:

An effective structure for organizing work orders and imposing control over their release is provided by SAP PM’s User Status Profile. You can construct a speedy approval procedure by establishing user statuses inside the profile, ensuring that orders match preset criteria before they are issued for execution. Improved maintenance operations are a result of the deployment of User Status Profile, which increases order management process efficiency, compliance, and transparency in SAP PM.

The post User Status Profiles: The Key to Effective Maintenance Order Management appeared first on ERP Q&A.

In order control profile – OPJK we will see the list of overall capacity profile under capacity avalilability check tab. By seeing that I thought this will do the capacity check and do the rescheduling the orders while creating the production order. But its not working in that way.

System will only check the capacity using the overall profile and tell us that the capacity is available on the scheduled date or not. If the capacity is not available, then we need to run the capacity leveling manually.

Here we will see the configurations for the capacity overall profile in top down approach.

The overall profile is the main thing that will do rescheduling the orders by checking the capacity in workcenters via CM25.

Main Part

Let us go to transaction CM25 Which is used for capacity leveling.

In CM25 it is asking for Overall profile.

First we will create one overall profile – OPD0 by copying the standard overall profile SAPCRPG001

Here system is asking for multiple profiles inside the overall profile.

The standard input/output of overall profile SAPCRPG001 in CM25 is below.

Now we will change the profiles one by one and see the changes in output of CM25

Selection profile – OPD1 you define all the parameters for selecting and displaying object for which you want to see the capacity requirements and the available capacities.

I copied the standard selection profile SAPSFCS001 and changed it in Overall profile.

Here the object set and filter set will define the input screen of the CM25.

The requirements grouping defines all the the capacity requirements groups that are assigned to the planning table.

The selection key defines the selection criteria used to select. mark or highlight operations online on the planning table.

Also you can define which order to be displayed in output in selection profile – Either planned orders or Maintenance orders.

Two outputs are shown below after changing Object / filter set values in selection profile.

If you want to do capacity scheduling only for some orders then change the selection profile.

Two pictures shown below after changing Requirement Group

Time Profile – OPD2 – basically defines the horizon for Capacity planning.

One year profile will have days range of 365 and 3 months will have days range of 100 days.

Two Pictures after changing the time profile from 3 months to 1 year profile

3 months profile shows timeline till june 2023

1 Year profile show timeline untill march 2024.

If you have longer production time then use longer time profile. Becasue if you use small time profile the orders will not be scheduled outside the time profile.

Control Profile – OPDE – This will control when to lock the production order. At the time of CM25 execution or while saving the orders in CM25 after dispatch.

Also we can define how the planning table to be displayed – Tabular / Grapical. In fiori the Grapical method will not work. So better use Tabular planning table. Or else use special apps for doing the capacity leveling.

Note: Period Profile is mandatory for Tabular planning table

After changing the Presentation layer to tabular got below results.

Strategy Profile – OPDB – This will control the dispatching sequence, finite scheduling, canceling dispatching due to error, planning direction, rescheduling with production version.

Dispatch sequence – Some times user may ask to schedule old orders at first and then schedule new orders

We can do this by changing the dispatch sequence.

For creating the dispatch sequence on your own you should create the sort fields and to maintain the sequence for selecting it.

Here I am going to create two sort fields (Layouts Key) based on it i need to do dispatching.

1. Production orders
   
2. Planned orders.

Go to CY39 and create it first by clicking create on top

In next screen click new entries.

Then give name and description and save it.

Now we have to edit it in same CY39 and to add the respective fields one by one.

Give the newly created layout and click edit

If more fields needed add more sructures by clicking new entry

Inside this just add the structure first by clicking the structures.

After adding the structure you will get the list of values. From here select the list of fields on which you need to sort the orders and to schedule it. Then click sequence / Heading and choose the acending or decending order.

Do the same for all layout queues and save it.

Then go to CY40 and assign the layout keys in it.

Give the new sort key and click enter and in next screen click new enteries.

Here you need to select the layout keys, which you have created under one sort key and save it.

Now this sort key you need to assign it in Dispatch sequence of the strategy profile.

Now you have to assign this to your overall profile. So that you can schedule the orders on your wish. Here the priority is given to production orders first and then to the planned orders.

So the production orders will be scheduled first and planned orders will be scheduled next.

Once after configuring all you just go to CM25, Give the inputs , Execute, and select all the orders by clicking shift + left click, Click dispatch (Green button) and save it.

After saving it you will get the output as below.

After dispatch all orders will be scheduled in a line. No overlapping will be there.

COOIS report

Here the orders are scheduled one after the other.

if there are incomplete dispatched orders are there the we need to schedule capacity leveing job on daily by two means.

1. Deallocate
   
2. Dispatch

Incomplete dispatched orders will not be considered by CM25 for rescheduling. So we need to do deallocation 1st and then to dispatch it again to follow a sequence in factory for producing materials.

The post Capacity leveling Overall profiles – Configuration appeared first on ERP Q&A.

Production Resource Tools (PRT):

• To perform certain operations in a Production/Maintenance order, the worker responsible for performing the task requires resources. In the SAP System, these resources are given the term production resources/tools.
  
• PRT is a moveable (not stationary) operating resource that is used in production or plant maintenance and can be used repeatedly. For example portable drilling machine, spanner, cutting tool, drill bit, electrodes, drawings, CNC programs, Vernier caliper, etc.

You can create PRT with the following types:

• MATERIAL PRT
  
• MISCELLANEOUS PRT
  
• DOCUMENT PRT=
  
• EQUIPMENT PRT

In a manufacturing industry, we keep using various tools during productions and these tools require maintenance to keep them usable. Maintenance of such tools normally depends on their usage in the production operation. These tools can be considered as Production Resource Tools in SAP and can be integrated with Plant Maintenance to trigger a maintenance activity based on the usage confirmation on production order.

This blog post will discuss how to set this process in SAP to integration PRT used in production with plant maintenance.

Steps:

1.1….. Create equipment with category P (PRT) – TCODE IE25

1.2….. Create characteristics with UOM similar to production unit. – TCODE CT04

1.3….. Creating measuring point as a counter for that equipment. – TCODE IK01

1.4….. Create measurement document for initial reading to activate. – TCODE IK11

1.5….. Create maintenance task list. – TCODE IA05

1.6….. Create maintenance plan. – TCODE IP01/IP41

1.7….. Attaching a measuring counter to PRT Equipment. – TCODE IE02

1.8….. Change routing and assign PRT equipment to operation. – TCODE CA02

1.9….. Create production order. – TCODE CO01

1.10… Confirmation of production order. – TCODE CO15

1.11… Check the measurement document – TCODE IK13/IK17

1.12… Run deadline monitoring for the maintenance plan. – TCODE IP30

1.13… Check the list of open orders against PRT. – TCODE IW38

The post Production Resource Tool Integration with PM & PP appeared first on ERP Q&A.

For example, we can trigger workflow to production manager when scrap is recorded in the production or we can create another order or operation when rework is recorded, etc. We can trigger production order relevant functions based on production order status (system or user) only.

Requirement: We have a list of operations for our finish product namely as CED coating, Assembly, Painting & Packing. The Painting operation is an automated process done with robot painting. If there is any painting rework then a labour do the manual painting on rework part & then Packing operation is processed. This is the regular process followed & there is rework in every manufactured lot.

Pre-requisites:

1. Create a Control Key with rework indicator active.

Control key: It is an user-defined key that determines how any operation will be handled at time of order processing and in product costing. There are different function which can be activated e.g. Scheduling, Print, Cost, Rework, etc.

As per the requirement, check the rework indicators. For system to consider any operation as rework operation, Control key with rework indicator checked should be used.

Note:

• Initially, A rework operation is not taken into account when scheduling task lists.
  
• If rework operation is last operation, then no automatic goods receipt can take place for the rework quantity. You must manually post the goods receipt for the quantity successfully reworked.

2. Create a ROS for rework (T-code-CA11).

First, create a paint rework work center for labour to record activity data.

Assign this rework work center to rework operation of reference operation set (ROS). This ROS will be used for reworking paint defect manually.

3. Create Trigger Point (T-code-CO31)

In trigger point select, function as Insert reference operation set. After selection insert ROS function assign the ROS group in parameter tab. Also, you can give after which operation you want this ROS to be inserted. In our case operation 0030 is painting operation & rework will be performed after painting operation. Hence, we will assign after operation as 0030.

Routing Setup:

Go to operation overview screen>>>click on go to>>>select trigger point overview.

Assign the trigger point to painting operation.

Click on StdTrgPoint to assign already created trigger point.

Test scenario:

Assume, We have a production order of 1000 qty. for 96240868 Side stand (Final Product) & in that we have found 50 qty. that need to be reworked for painting.

First, do the following steps:

• Create a production order with standard order type for production (PP01).
  
• Release order.
  
• Good issue to order.
  
• Confirm the first four (OP10, OP20) operations.

• Go to confirmation of painting operation (CO11N).

We had a production lot of 1000 qty. In first two operation (CED coating & Assembly) there was no rework rejection. In third operation (Painting) confirmed ok quantity was 950 qty. & there was rework of 50 qty. Once we save the confirmation with Rework quantity. Trigger point will be triggered & rework operation of reference operation set (ROS) will be assigned to production order. In that rework operation, operation quantity will be 50 qty. (rework quantity of paint operation).

As we are using manual trigger point, That’s why system is giving this pop-up. Whether you want to execute the trigger point for rework operation or not.

Select the function & click on execute.

After executing, confirmation will be saved & rework operation will be added to production order.

• Display Production order:

We can observe that after OP30 an operation has been added as painting rework manual OP32.

• Confirm the rework operation after completion.

We can see that operation qty. for the rework operation is 50 qty. as there are only 50 qty. rework in OP30.

(Note: If you try to skip rework operation & do confirmation of OP40 then yield confirmed qty. will 950 qty. only.)

Save the confirmation OP32.

After this, you can go ahead with the confirmation of last operation & Post the GR against production order. Complete the further process (TECO, Settlement, CLSD).

The post Rework Operation of ROS assign to Production Order using trigger point. appeared first on ERP Q&A.

Here we will see how we can use the Handling unit in production planning.

Handling unit is SAP term for packing materials in box. Creating HU will create data on packing materials in boxes

Some times Production team will do the packing of materials in production area and ship it to warehouse. So we need to configure the SAP for HU from Production side.

Let us consider we are producing a mobile packed in box.

First we are packing the mobile in plastic cover and then in cardboard box.

In BOM of mobile we will include this plastic cover, cardboard box and some spare parts.

we will create the production order for mobile and consume the cover and box for it. At last we will create one handling unit for the production order and post the goods receipt with HU transaction.

Mostly business will have specific details for each box at multiple levels for tracking purpose. So for creating the specific data in SAP we will use handling units.

Main Part

Configuration needed

1. Packing Material Type
   
2. Packing Material Group
   
3. Assigning material type to material group

We need to define the packing material types – VHAR i.e. cover or box

Now we will create group the and assign the cover and box in it. We can assign this group to the packing material in material master.

Packing Material Group – VEGR

Mostly we will use this to restrict the groups to certain plants by using authorization

Now we will assign the packing material types to the material Group – VHZU

Master data.

1. Material to be packed (Mobile) – Normal Material FERT / HALB / ROH any
   
2. Material used to pack (Cover / Box)
   
3. Packing instruction
   
4. Packing instruction determination procedure
   
5. Production Master data – Routing, BOM, Production version

Material to be packed can be any type ROH or FERT. I am using FERT

Now we will create the packing material (box/cover) with material type VERP and above packing material type and group in sales – general/ plant view.

Packing instruction – POP1

Here we will define how many mobile will be packed in a single box or cover. I am going to pack 1 mobile in 1 cover and after packing the mobile in cover inside a box. So I am creating cover as subordinate packing instruction.

now Mobile > Cover > Box has been done.

Packing Instruction Determination – POF1

Here we will define which PI to be selected for which material.

In HU02 or COP1 screen while creating Handling unit the system will determine the Packing Instruction for the materials automatically.

Here for production COP1 and Warehouse HU02 we have to use STOC determination type. For sales VL01N we need to use SHIP.

Assign the PI to the material and save.

Now creating the Handling unit for the production orders.

Packing Materials using production order – COP1

Go to COP1 and put the production order.

Doing GR for Handling units – COWBHUWE

For this order no auto GR control key should be assigned to any operation as the the GR in COWBHUWE will not work

Click enter to get the next screen and the PI got selected automatically.

Now go to COWBHUWE to do the GR for handling unit.

Monitoring HU – HUMO

Now if you want to see the list of HU you can use HUMO to see the list. Also in MMBE we can see it.

Double click on line item to see the details and content.

Repetitive Manufacturing

Packing – MFP1

GR in REM – MFHU

The post Handling unit in Production Planning – Step by Step guide appeared first on ERP Q&A.

Most of us know the Over delivery and Under delivery tolerance use for Purchase Order. SAP has provided similar kind of function for Production/ Process order. I was unable to find the blog on this functionality so decided to make one.

Here I will try to explain the use of Over delivery and Under delivery tolerance.

Our aim will be, How over delivery and Under delivery tolerance impacts on Production/ Process orders and how we can control the system using it? How this can help us and user for more stable SAP system?

Pre-requisite:

1. Go to Material master, work scheduling view, and maintain Over delivery and Under delivery tolerance as per requirement.
   
2. OPK4 config for “Order Confirmation Parameters”.

Please check below screen shots.

Process:

Case 1:

Under delivery tolerance maintained as 5%. Over delivery tolerance is not maintained.

Configuration set as error for Under delivery tolerance and not checked for over delivery tolerance.

Now created Process order for Material – 100119 & Plant – 2002 for Quantity – 100.

After that please complete the Goods Issue against process order and Confirmation of process order.

After that once we reach for Goods Receipt against order in to MIGO transaction then maintained config and master data will impact.

But here system provided warning message against it. But as per earlier configuration in to OPK4 we set as error message.

To change warning message in to error message we have to make changes in to OMCQ transaction. Please check below screen shot.

Here we have to change “W” into “E” for error.

After changing we will do Goods receipt against process order again then system will give below error.

Conclusion: System provided error as per master data and config.

Case 2:

Under delivery tolerance is not maintained. Over delivery tolerance is maintained as 5%.

Configuration set as not checked for Under delivery tolerance and error for over delivery tolerance.

Now created new process order for Material – 100119 & Plant – 2002 for Quantity – 100.

After that complete the Goods issue against the process order.

Now we will do confirmation for process order in to CORK transaction.

For that we will change the yield quantity of process order from 100 DR to 110 DR. After changing quantity if we tries to save the confirmation then system provides below error.

Conclusion: System provided “Overdelivery is not permitted” which will prohibits us from entering wrong quantity.

Case 3:

Under delivery tolerance & Over delivery tolerance both maintained as 5%.

Configuration set as error for both Under delivery tolerance and Over delivery tolerance.

Now created new Process order for Material – 100119 & Plant – 2002 for Quantity – 100.

After that complete the Goods Issue for process order. Now we will do confirmation for process order in to CORK.

For that we will change the yield quantity of process order from 100 DR to 106 DR. After changing quantity if we tries to save the confirmation then system provides below error. Because yield quantity is above tolerance limit.

Now we will change the quantity below our under delivery tolerance and will try to confirm the process order.

Here, system did not provided any error for under delivery tolerance.

But now we will do Goods Receipt against process order in to MIGO transaction.

Here system provided error for under delivery.

Now we will change the quantity from 94 DR (which is out side of under delivery tolerance) to 95 DR (which is as per under delivery tolerance).

Conclusion: System checked tolerance limit and provided no error as quantity is as per Tolerance limit.

The post Over delivery and Under delivery tolerance for Production/ Process order appeared first on ERP Q&A.

Status profile: A status profile contains the individual user statuses and the business transaction rules defined for those statuses. You can define multiple limit number of user status profiles that can be maintained in SAP system.

Rework order: As we all know that rework might be of different problems/issues. These issue can be solve by single operation or might take multiple operation. It is also possible that even after doing the rework our product can not be use or fulfil our desire results.

Business Requirement:

Client has 5 operations, in that for the last operation they want to do rework if there is any rework quantity for Burr/dent issue only. Rework order should be created automatically if there is burr on the material. For reworking the burr, they use a specific operation called buffing. They want that cost of rework should go to main/actual production order.

Pre-requisites:

1. Create Status Profile: (T-code-BS02)

First we need to create a status profile.

Create a status profile as Rework & give a user status ZRW (Rework Order Created). Select Object types as PP/PM: operation.

2. Create Reason for Variance: (T-code-OPK5)

As per the requirement we have to create a reason for variance i.e. burr on material.

Create a reason for variance as ZRW (Burr – Create Rework Order). Assign the user status (Rework) & select the user status (ZRW) to this reason.

3. Create a ROS for rework (T-code-CA11).

As they will be using only buffing operation so we will create an reference operations set (ROS) with buffing as operation.

Rework ROS: Assign rework work center & give name to the operation.

4. Create Trigger Point (T-code-CO31)

In trigger point select function as: Create order with reference & assign the user status profile ZRW that we have created with help of status profile.

In parameter maintain below details:

1. Assign User status as ZRW.
   
2. Group & Group Counter: ROS that we have created.
   
3. Order Type: ZRW (Rework Order Type).

Setup:

1. Assign status profile to standard order type in (T-code-OPJH).

As we are dealing at operation level therefore assign status profile to operation level.

2. In main routing assign, the trigger point to last operation OP50 (T-code-CA02).

Open Routing>>>Go to operation overview screen>>>click on go to>>>select trigger point overview.

Assign the trigger point to last operation (OP50).

We are able to see that trigger point is assigned to operation 50 which is our last operation.

Testing scenario:

We have a production order of 50 qty. & in that we have found 10 qty. that need to be reworked for burr.

First do the following steps:

• Create a production order with standard order type for production (PP01).
  
• Release the production order.
  
• Do the goods issue to production order with help of MIGO.
  
• Also, Confirm the first four (OP10, OP20, OP30, OP40) operations in CO11N.

We are considering that we have not found any burr related issue in the first four operations.

1. Go to confirmation of last operation (CO11N).

As mentioned above maintain rework quantity as 10qty.

Once you save the confirmation with Rework quantity & reason for variance as Burr (Create Rework Order).

Trigger point will be triggered & will create a Re-work production order.

2. Now to see the re-work order go to COOIS.

We can see that the rework order has been created with order type ZRW of 10 qty.

3. Open rework order & go to settlement header.

We can see that rework order needs to be settled to parent production order (Main order PP01).

That means the cost for rework will be booked to main order.

Note:

Automatic & manual creation of order can be controlled by trigger point with ACTIVATE function in parameters.

4. Check main production order:

User status has been updated as ZRW for the operation.

Process Flow:

The post Rework Order creation for specific reason using trigger point appeared first on ERP Q&A.

Benefits of Change Record

Key Features

Fiori App Required

1. Global Process route Workbench
   
2. Myinbox
   
3. Manage Change Record / engineering Changes,
   
4. Manage Team and Responsibilities

Required configuration

1. Define Number Range for the change Record

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Number Range Interval for Change Record

2. Define Object types

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Object types

Note : The object types are predefined

3. Define Object Categories

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Object Categories

Note: These are predefined Category

4. Define User Status

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Status

5. Define User Action

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Action

The User Action Text Defined appear on the front end screen of the Change Record

6. Define User Action Profile

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Status Profile

As seen in the above screenshot, conditions help to navigate to different status from the current status, as in this case the status is 10, so when the change record is in status 10, then it can be moved to either 10,30,15 manually or via background task.

7. Define Item Relevance

Path : SPRO > Logistics General > PLM > Change Record > Setting for engineering Changes > Define Item Relevance.

This item relevance is used for the Items mentioned in the change record as shown in the image below for each of the object types. The control whether the enable the display the field of change relevance is covered by the configuration Define Engineering Record Type Section in Image 18

8. Define Engineering Record types.

Path : SPRO > Logistics General > PLM > Change Record > Setting for engineering Changes > Define Engineering Record Types

The change number and the status profile defined are assigned to the change record type Z01.

The check “ProcStatus” is used to control whether the item processing status is required or not as shown in the below image

SAP recommends the use of Process route for the Engineering change’s so the Check box Proc Route is enable for the Change record type : Z01.

Para Check column is used to enable the check whether same Object is used parallelly in other change number which is open or in process

The Reference Object that will be used for the change record type are updated. You can create Multiple change record type having different Reference Object

Mapping of the Item Relevance with Refence object category is done in this node. As per the mapping only the relevant item relevance will be shown.

The Configuration in this Node decide, control at which user status the Change number is created in SAP and at which user status the change number created in SAP is marked as completed. The Change number created in SAP is seen at the header of the change record also via the cc03 transaction.

It is also possible to control whether the change number should be created with released key or without release key. The below parameter defined in the creation attribute decides whether the change number creation attribute, if its blank its “without release key” and if its set to 1 its ”Release Key”

it is possible to define the digital based on the User action as defined in Section 6

9. User Assignment to Receive Task

Transaction : PFTC

If you want to control the Work items from the change record to be displayed to specific set of People then assign the user by navigating to

Additional Data > Assignment > Maintain

if you want the workflow task to create workitem as per the user id mentioned in the task created for the process route then Change the attribute of the task to General task as shown above by clicking on the Attribute button.

10. Activate Event linkage

Transaction : PFTC

11. Enabling Service for MyInbox

This service is used to allow the processing of the work items generated, for the change Record.via the MyInbox App. if this service is not enabled you will be able to see the work items in the list of the Myinbox app but you cannot open / Process it

13. Define Activities for the Change Record Processing

Path : SPRO > Net weaver > Application Server > Basis Service > Records Management > Customization for Process Route > Create or change Activities and Activity Functions

Here all the Activities for the case management are defined but to filter out the relevant activities for the change record the below configuration is required, only after which you can the activities in the change record.

the above activity is required to change the status of the change record automatically based on the rules defined in the BRF+ application.

14. Define Activities for GOS Objects

Path : Spro > Logistics General > PLM > Change Record > Process route > Define Activities for GOS Objects for Process Route

Change Record Processing

1. Create Change Record

2. Fill the details in the Change Record

Add Objects to be changed via the change record

Add activities that needs to be performed for the change record. the task Can be performed Sequential, Parallel or in Background, for the sake of the Simplicity i have added the Agent for the task as a user there are other options that can be explored of, From HANA 2021, there is provision to update the Team as well which is created via the Fiori App : Manage Team and Responsibilities

the background task are not automatically added they are added as either a sequential task or parallel task, the task shown in the below image is to update the status of the change record Automatically based on the condition, which is explained further.

The task can also be added via the Template method. To Create Template Fiori App : Global Process Route Workbench is used

Template Created via the Global Process Route Workbench. The Task / Activity shown below are just for demonstration in this example are not in sync as per the status of the change record.

If there is further requirement which is almost certain. to have the template loaded automatically in the change record based on certain condition like record type, status etc, that can be done via the BRF+ Application.

The BRF + application and its functions need to be assigned in the configuration. Note: The BRF + application needs to be activated in order to have it working

BRF+ Application Creation and Assignment

Create a BRF+ Application and add a function to it by right clicking. Set the mode of the function to either functional mode or Functional or event mode.

Note: for the folks who are new to BRF+ or still not aware of the functionality. Context is the input part and result data object is the output part.

the translation of the data from the input to output is done via the expression. In the image below the Input conditions acts as a expression

Define the Context: its a structure with binding to DDIC

the output is defined as Element and has a DDIC Binding

Create a Decision table as a Top Expression, the inputs fields to the Decision table is from the context and the output is from the Results Data object.

Assign the BRF Application in the configuration Path

Path : SPRO > Logistics General > PLM > Change Record > Process Route > Define Template

Change Record Process Continuation.

Start the workflow in the change record.

the work item will be received in the my inbox App or in the SO01 Transaction. Complete the Task to move the change record to the next task as per the process route.

Change the status of the Change record. The status of the change record are as per the Section 6 ( User Action Profile )

if the request it to Update the Change record status based on the previous task decision that can be done via the BRF + Application. SAP has Predelivered standard task for the Changing the Changing status automatically based on the BRF+ Setup

Create Background Task

SPRO > Netweaver > application server > basis service > Records Management > customization for process route > Create or Change activity and activity type.

Create Background Service

Path > SPRO > Logistics General > PLM > Change record > Process route > Define Background Service

Now as per the above image the change number is not created yet for the change record, but if we see the configuration defined for the change Record Image 19,20, 21, We can see that the change number is created only once it reaches the status 40. Please refer the below image where the change record is updated with change number of attribute with release key.

Perform the changes via the change number and Release the change number. After the changes are performed, the change record is updated. Once the change reord reaches the status complete the change number created is also completed.

Refer the Configuration Section Engineering Record type : Image 19

The post Change Record in S4HANA – A New Look to ECR/ECO in S4HANA appeared first on ERP Q&A.