FIX THE COMMIT / SORTING FUNCTION

FUNCTIONALITY AND PPF EXCEPTION

PROCESS

Planning S&P
September 2020

INTERNAL
NXP, THE NXP LOGO AND NXP SECURE CONNECTIONS FOR A SMARTER W ORLD ARE TRADEMARKS OF NXP B.V.
ALL OTHER PRODUCT OR SERVICE NAMES ARE THE PROPERTY OF THEIR RES PECTIVE OW NERS. © 2020 NXP B.V.
B AC K G R O U N D

• The main requirement of the War on Manual Touch was to solve below situation for FCE customers:

− when the orderbook is updated, shift of confirmations (CMAD’s) can be perceived

− this is because of the sequence of scheduling operations (first cancellation/qty. decreases; new order creation is last operation)

− released/put back CTP is not reused to improve mismatches

− creation of new sales orders may end up with RMADs / CMADs out of sequence

• above scenarios drive email communication between CSRs and PPFs to restore the lost commit or put the RMADs /

CMADs in sequence

• To overcome above, an Excel-based macro was introduced and used bi-weekly (Miguel’s macro)

• The aim of this macro is to rearrange the confirmations based on requested delivery date

INTERNAL 1
SOLUTION

• To automate the process, an SAP change request was initiated (CHG0046932, approved by Coby in Dec. 2018)

• The automated sorting will go live in WK40 and will cover for scheduling process only:

− Re-sequencing the orderbook by RMADs / CMADs (sorting function)

− Triggering a CTP check for OB lines where there is a mismatch

− Other CSC related changes

INTERNAL 2
Fix the commit: Sorting function

INTERNAL
NXP, THE NXP LOGO AND NXP SECURE CONNECTIONS FOR A SMARTER W ORLD ARE TRADEMARKS OF NXP B.V.
ALL OTHER PRODUCT OR SERVICE NAMES ARE THE PROPERTY OF THEIR RES PECTIVE OW NERS. © 2020 NXP B.V. 3 INTERNAL 3
SORTING FUNCTION / OVERALL CONCEPT :

• To re-sequence the OB:

‒ The earliest requested delivery date (RDLY) will get the best CMAD
‒ To ship in sequence to customer → Order with earliest RDLY to be delivered first

INTERNAL 4
S O R T I N G F U N C T I O N – Z V C M X PAR A M E T E R S :

− New ZVCMX parameter created at customer ship-to – material level to activate/de-activate the sorting function
(‘CMAD Sorting Func.’ field)
− Sorting Function will be switched on for all materials except of PPF’s exclusion list – see next slides

INTERNAL 5
S O R T I N G F U N C T I O N – Z V C M X PAR A M E T E R S :

− If Sorting Function is activated:

▪ the 1st sorting is executed automatically before the start of scheduling to make sure starting situation is sequenced correctly
▪ the 2nd sorting is executed automatically after scheduling

− Sorting possible to invoke manually in Scheduling tool

− Only orders are included that are relevant for scheduling (depending on ZVCMX settings: Match Orders by PO,
Match Order Reason and Match CPN in SO).

INTERNAL 6
SORTING FUNCTION / INCLUSION - EXCLUSION :

• This new SAP function is created for sorting the confirmed schedule lines

‒ Logic of Sorting Function will consider the Partial Deliveries settings in Customer Master

‒ Exclude:
‒ MSO direct shipments with a value in the credit-block field of the schedule line or with Internal PO
‒ Orders where AS, 04 and Z3 blocks are set at schedule line level

‒ Include orders with PR block – PR tolerance will be re-calculated after sorting (might be removed or put back
based on PR rules)
‒ Note: PPFs should not use manual PR block on schedule line level to block ship-outs (e.g.: quality/stock issue), since the
sorting can run in parallel and remove PR block → manual AS block on schedule line level should be used instead

‒ Sorting will consider the plant of the orders - only CMADs from the same plant will be considered during the
sorting
‒ Sort function will consider the delivery unit (PQ) from the material master → if a confirmed schedule line is out
of PQ, it will be excluded from the sorting

INTERNAL 7
S O R T I N G F U N C T I O N / T R AC K I N G :

‒ Special user ID CMAD_SORT to identify changes triggered by the sorting function

ZCPLOG table:

Same user ID
CMAD_SORT can
be seen in Sales
Order/Change Log

‒ New table called ZSORTLOG to include changes from the sorting function / audit trail
Table can be accessed through ZSE16 transaction - The possible action codes visible in ZSORTLOG:
• N = no change on that schedule line
• D = schedule line deleted by sorting
• I = schedule line inserted by sorting
• R = a schedule line where there was an attempt of CMAD update, but couldn’t go through because the RMAD > new CMAD

INTERNAL 8
PPF Exception Process

INTERNAL
NXP, THE NXP LOGO AND NXP SECURE CONNECTIONS FOR A SMARTER W ORLD ARE TRADEMARKS OF NXP B.V.
ALL OTHER PRODUCT OR SERVICE NAMES ARE THE PROPERTY OF THEIR RES PECTIVE OW NERS. © 2020 NXP B.V. 9 INTERNAL 9
PPF EXCEPTION PROCESS:

• PPF’s requirement to exclude some 12NCs from the sorting, e.g.: Escalation Record or CMM, special cases (e.g. batch
managed shipments – lot No. assigned to specific sales order No.)
• 12NC exclusion should be carefully used and not regarded as default → Goal is to have fewest possible exclusions

‒ ADD to the exclusion list :

The exclusion list can be updated any time on SharePoint by planners
On Mondays, COD will look at the file and turn off the sorting function for those 12NCs to be excluded

‒ REMOVAL from the exclusion list :

If a 12nc can be removed from the exclusion list, PPF will update the file
Next Monday COD will turn on the sorting function for those 12NCs to be included again

If a 12NC is turned to OFF (sort function inactive), CSRs SHOULD NOT TOUCH ‚SORTING’ FIELD IN ZVCMX!
If, in between two Mondays, there is an urgent request from PPF to exclude a 12NC from the sorting, NEXT TO adding the
12nc to the Exclusion list, you need to reach out to all affected CSRs to change the setting manually (in ZVCMX).

INTERNAL 10
MAINTE NANCE PROCESS :
P P F - AD D S / C O D – D E - AC T I VAT E Z V C M X S O R T I N G F U N C T I O N

Any time during the week:

- PPF to add the 12NC to the sharepoint excel file by filling all 7 columns from '12NC' up to 'Reason for exclusion'
('Planner/date of add' = today’s date)

Every Monday by EOB TPE:

- COD to access the list in SharePoint and to select all 12NCs where COD add date = blank (means that the record is new
since last access)
- COD to go into SAP ZVCMX selection screen and insert: 12NC + FCE
- COD to go back into the list in SharePoint and set the COD/Date of add = today’s date

INTERNAL 11
MAINTE NANCE PROCESS :
P P F - R E M O VA L S / C O D - AC T I VAT E Z V C M X S O R T I N G F U N C T I O N

Any time during the week:

- PPF to fill in the sharepoint excel file in column 'Planner / Date of removal' where she/he has to insert today’s date

Every Monday by EOB TPE:

- COD to access the list in SharePoint and to select all 12NCs where PPF removal date not equal at blank and COD removal
date = blank (means that the record is to be removed since last access)
- COD to go into SAP ZVCMX selection screen and insert : 12NC + FCE
- COD to go back into the list in SharePoint and set the COD/Date of removal = today’s date

Note: Do not delete lines from the SharePoint file where the exclusion has been reverted as the data needs to be kept for
tracking/follow-up reasons

INTERNAL 12
M A I N T E N A N C E P R O C E S S : AD D S / V E RY U R G E N T R E Q U E S T W H I C H C AN N O T WA I T
N E X T M O N D AY C O D P R O C E S S

- If, for any reason, a 12NC needs to be excluded from the sorting in between two Mondays (urgent requests only), PPF to
reach out to the CSRs who have access to this field → CSR will change the field manually
- PPF to add the 12NC in the file and put the COD add date = today’s date
Note: NEXT TO adding the 12nc to the Exclusion list, you need to reach out to all affected CSRs to change the setting
manually (in ZVCMX).

M A I N T E N A N C E P R O C E S S : VAL I D AT I O N / M O N I T O R I N G
Once a month:
- CPO to access the list in SharePoint and to select all 12NCs where 'Planner / Date of removal’ is equal to blank AND
'Planner/date of add’ greater or equal than a month
- CPO to contact PPF to validate if the exclusion is still needed: if not, PPF to go thru the removal process immediately
- once the exercise is completed, CPO to fill in ‘CPO review date’ = today’s date + to add a comment in ‘CPO
recommendation’ column (OK to keep or PPF to do removal)
- trend will be reported to CSC MT via CPO scorecard

INTERNAL 13
G O L I V E AC T I O N S

Go Live is set for the 30th of September (WK40)

➢ PPF team to fill in the list in SharePoint for exclusions by latest the 25th of September (Friday)
Action: PPF organization to fill in list
Note: all items will be set as default to Sorting = Active that are not in the exclusion list

➢ ZVCMX field set to „Inactive” for all 12NC added to the Exclusion List by the 30th of September Morning

➢ From the 5th of October onwards, COD to manage the weekly process by TPE EOB on Mondays

➢ CPO to do the first review on the 26th of October

INTERNAL 14
Fix the commit: New Action Code

INTERNAL
NXP, THE NXP LOGO AND NXP SECURE CONNECTIONS FOR A SMARTER W ORLD ARE TRADEMARKS OF NXP B.V.
ALL OTHER PRODUCT OR SERVICE NAMES ARE THE PROPERTY OF THEIR RES PECTIVE OW NERS. © 2020 NXP B.V. 15 INTERNAL 15
N E W AC T I O N C O D E :

• DM action code:
‒ This action code runs in the background (never visible in the matching screen in ZCSPSCH)
‒ It triggers CTP check to find if there is better availability (CMAD improvement)
‒ DM action code cannot be manually inserted

• DM is added in case following conditions are true:

‒ A date mismatch occurs: the requested and confirmed delivery date are not the same.
‒ No quantity (e.g. QD) or date changes (e.g. PI) action codes are available
‒ The order line is not partially delivered (delivery status = B) or the purchase order number is added (MSO flow)
INTERNAL 16
Q&A

INTERNAL 17
RESOURCES

• Customer Program Trainings

• 12nc sorting exclusion list

• Contacts:
− Regional CSC SMEs:
▪ AMEC: Amado Nava, Kurt Wallach
▪ APAC: Mandy Ge, Queenie Xiao, Tina Xu
▪ EMEA: Elena Constanda, Mihai Botezatu, Dragos Bobeica
− CPO: Liliane Vincent
− CSC S&P: Alin Tudor, Carmen Fodroczy
− Planning S&P: Nora Luppej, Dan Dinu

INTERNAL 18
NXP, THE NXP LOGO AND NXP SECURE CONNECTIONS FOR A SMARTER WORLD ARE TRADEMARKS OF NXP B.V. ALL OTHER PRODUCT OR SERVICE NAMES ARE THE PROPERTY OF THEIR RESPECTIVE OWNERS. © 2020 NXP B.V.