de-mystifying customer cum's and requirements

De-Mystifying Customer CUM's and Requirements

Don Thompson EDI Coordinator

Continental Strucutral PlasticsMarch 22, 2010

Introduction – Don Thompson

Sr. EDI Consultant – RCM CorporationImplemented MFG/PRO Ecommerce and Gentran.

Worked with customer schedules and orders.

EDI Coordinator – Continental Strucutral Plastics Work with shipping departments resolve EDI issues.

BS Computer Science – Slippery Rock University

What We’ll Cover Today

• What are Cum Based Schedules.• How does MFG/PRO Handle them.• How will my Prior Cum affect MRP.• How will my Cum Shipped affect MRP.• What are Requirement Based Schedules.• How does Merge RSS affect my ship

schedules• Questions and answers

What are Cum Based Schedules

• 830/DELFOR weekly 03/15/2010 1000 03/22/2010 1000 03/29/2010 1000 04/05/2010 1000 04/12/2010 1000 04/19/2010 1000

• 862/DELJIT Daily 03/22/2010 200 03/23/2010 200 03/24/2010 200 03/25/2010 200 03/26/2010 200

• Prior CUM 03/15/2010 0

• Shipped CUM 03/15/2010 0

Setting up a Schedule Order as Cumulative based is done in Schedule Order Maint.

The Netting Logic in Schedule Order Maint tells MFG/PRO what logic to use to generate the required ship schedule.

1 - Use Ship schedule only for Req Schedule2 - Use Plan Schedule only for Req Schedule3 - Use Plan & Ship for Req Sched (replace)

Customer Plan Schedule Maint

Customer Ship Schedule Maint

Cumulative Shipped

Run Selective Req Ship Sched

Results that Drive MRP Notice how with netting logic set to 3 that the ship data has replaced the

plan data.

Now lets see the results when we set the Prior Cum Req to 19,000 and run the

selective update.

After running 7.5.6 Notice the 19,000 in the open qty? This is a result of our setting the prior cum to 19,000 but yet our Cum Shipped was 0 so it

believes that we are behind 19,000.

Now lets see what happens when we have a higher Cum Shipped then what our prior cum is

set to and how that will effect our MRP.

After running 7.5.6 Notice that there is no demand due until the week of 03/29/10. This is

because the prior cum is 19,000 but yet our Cum Shipped was 20,000 so it believes that we have over shipped the 1,000 and adjusts the schedule

accordingly.

Setting up a Schedule Order as Requirement based(example’s being Kanban, DO, RAN, SEQ, Order Number) is also done in

Schedule Order Maint.

When Setting up a Schedule Order as Requirement you will also be asked

Ship Complete %Merge RSS?Unique Days

Exclude Planning Data

Customer Plan Schedule Maint

Customer Ship Schedule MaintNotice the “RAN” info in the Reference?

Requirement schedules Open Qty’s are not affected by “CUMS”. In the following example our Prior Cum was 0 and our Ship Cum was 0 notice the open Qty’s? In Requirement schedules the qty will remain open until it is shipped or the qty reach’s the shipped

complete % set on the Schedule Order.

Requirement schedules Open Qty’s are not affected by “CUMS”. In the following example our Prior Cum was 20,000 and our Ship

Cum was 0 notice the open Qty’s still only reflect what is due vs in a CUM based schedule we would be passed due the 20,000.

Questions and Answers