I am trying to transfer AFKO-GAMNG field from communication structure to extract structure in LBWE transaction. Here I am getting error 'End phase 002************' Message no. D0322.
When you add or remove fields of an extract structure in the function for maintaining extract structures of the logistics extract structures Customizing cockpits (transaction LBWE), a termination occurs due to an error during the generation of the structure.
The error message issued by the data dictionary is "End phase 002" and corresponds to message D0 322.
The same symptom can occur during the import of the structure change into a system.
1. Appends were created manually in the edited extract structure and not automatically with the Customizing Cockpit (LBWE).
2. Fields are defined twice in an extract structure, and the extract structure is not active.
3. In the extract structure itself there are no problems, but there are activation errors in a customer-specific structure or table which also includes includes of the extract structure.
4. When you change the extract structure using the Customizing Cockpit (LBWE), the user append (ZZMC...)was assigned to a non-transportable development class.
5. You can transport the assigned development class but the transport layer is not compatible with the MCEX development class (SAP transport layer) of the carrier include (for example, the consolidation targets are different).
Solution
For 1+2) Note that manual appends (unlike the appends created with transaction LBWE) are not supported by SAP.In the case of manual changes to extract structures (or their includes), problems and inconsistencies are almost inevitable.
Delete all appends not created using transaction LBWE for the affected extract structure. All extract structures must be active.Then repeat the transport of the changes from the development system into the target systems.
For 3) Using transaction SE11, find the include of the extract structure that cannot be activated.Try to activate this include directly using transaction SE11.
In the activation log you should now be able to see the reason for the failed activation. A where-used list for the include may also help.
Then solve the activation problems of all dependent DDIC objects.
For 4) If the user append structure was inadvertently assigned to a non-transportable development class, the assignment should be corrected according to the procedure described in note 442583. The program correction described there may be necessary.
For 5) Adjust the settings of the transport layer of the development class used to the settings of the SAP transport layer.
you have check the note given by Anil in OSS notes..
Please check the same note 623411 here.
Symptom
When you add or remove fields of an extract structure in the function for maintaining extract structures of the logistics extract structures Customizing cockpits (transaction LBWE), a termination occurs due to an error during the generation of the structure.
The error message issued by the data dictionary is "End phase 002" and corresponds to message D0 322.
The same symptom can occur during the import of the structure change into a system.
1. Appends were created manually in the edited extract structure and not automatically with the Customizing Cockpit (LBWE).
2. Fields are defined twice in an extract structure, and the extract structure is not active.
3. In the extract structure itself there are no problems, but there are activation errors in a customer-specific structure or table which also includes includes of the extract structure.
4. When you change the extract structure using the Customizing Cockpit (LBWE), the user append (ZZMC...)was assigned to a non-transportable development class.
5. You can transport the assigned development class but the transport layer is not compatible with the MCEX development class (SAP transport layer) of the carrier include (for example, the consolidation targets are different).
Solution
For 1+2) Note that manual appends (unlike the appends created with transaction LBWE) are not supported by SAP.In the case of manual changes to extract structures (or their includes), problems and inconsistencies are almost inevitable.
Delete all appends not created using transaction LBWE for the affected extract structure. All extract structures must be active.Then repeat the transport of the changes from the development system into the target systems.
For 3) Using transaction SE11, find the include of the extract structure that cannot be activated.Try to activate this include directly using transaction SE11.
In the activation log you should now be able to see the reason for the failed activation. A where-used list for the include may also help.
Then solve the activation problems of all dependent DDIC objects.
For 4) If the user append structure was inadvertently assigned to a non-transportable development class, the assignment should be corrected according to the procedure described in note 442583. The program correction described there may be necessary.
For 5) Adjust the settings of the transport layer of the development class used to the settings of the SAP transport layer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.