Fields missing in import and export structure PPCO0001 - PPCO0023

Question

Hello Experts,
I'm hoping that you can help me.  I am trying to add some logic in user exits to default data and do some checking in production orders.  It would be great if I could talk to you about what Iu2019m trying to do and the problem that Iu2019m running into.
My main problem is that in the exits provided (enhancements PPCO0001 u2013 PPCO0023), most of the time either fields being imported or the field being exported do not include the fields that I want to change or check.  Iu2019m wondering if there is some way to just pull-in the data and change/check in addition to what is already available to the exit. - Can I append the structures?
Hereu2019s an example below:
u2022     PPCO0006 Enhancement to predefine fields in order header
With this enhancement you can take fields from the order header in your own program and process them or define values for them and transfer the changed data again to the standard system. The transfer to the system takes place before you reach the order header screen. EXIT_SAPLCOZF_003   Exit for predefining fields in order header.  The fields in the order header (structure CAUFVD) are placed in the function exit. All the fields that you can define or change are defined in the structure HEADER_CUST. The contents of HEADER_CUST is transferred back to CAUFVD on leaving the function exit.
Problem 1.
The documentation sounds greatu2026. Seems like the right place --  all the data I need is supposed to already be in CAUFVD_IMPu2026. BUT HEADER_CUST and HEADER_CUST_EXP do not have the fields that I need change.  If I try to append the structure and include additional CAUFVD fields I either get a warning in the activation because of duplicate fields or If I try to add them as Zfields the program doesnu2019t take the change data because it does a move-corresponding from HEADER_CUST_EXP to CAUFVD and the Z fields donu2019t match.  - what is the correct way to change header values if the fields that you want to change are not already defined in the structure HEADER_CUST?
Problem 2.
It seems that this exit occurs prior to pulling in the data from the standard routing (which would normally populate CAUFVD-PLGRP ... at the time of the exit this field is blank so i cannot use it to determine the value for another header field.  I could get around this by reading directly PLKO but that won't help me if I cannot add CAUFVD-FEVOR as a field availble for changing/defaulting.
Problem 3.
If I get around Problem 2, I still have another problem.  In PPCO0007& PPCO0001 I'm trying to change the user status to block the order from being printined until it passes the validation check and is error free.  In PPCO007 I can block the order from being saved or in PPCO0001 I can raise a message that an error was found... but I need to change the user status at the same time as rasing the error or blocking the save.
Thanks so much for any guidance that you can give.

Answer 1

Dear,
When you do so, in the PPCO0001 customer enhancement, you should carry out follow actions based on the status changes since the contents of the STATUS_TABLE and STATUS_TABLE_OLD  Exist is EXIT_SAPLCOBT_001  and  CALL FUNCTION 'STATUS_CHANGE_EXTERN'
For details refer the OSS note 86553
Hope it will help you.
Regards,
R.Brahmankar