Solution : https://service.sap.com/sap/support/notes/522246 (SAP Service marketplace login required)
Summary :
This SAP Note discusses issues related to conversion exits for external and internal number transfers within the Project System (PS). It emphasizes the importance of one-to-one correspondence between external and internal numbers for WBS elements in a client. These numbers play integral roles in database keys and must be uniquely maintained across different clients to ensure consistent data handling. Conversion processes between external and internal numbers are facilitated by specific SAP modules, including CONVERSION_EXIT_KONPR_INPUT and CONVERSION_EXIT_KONPR_OUTPUT among others. The note highlights automated and manual invocation of these conversions, flagging potential issues when external numbers do not align with project coding structures. Moreover, it outlines the implications of copying these elements across systems or clients and stresses the non-modifiability of external numbers in distributed systems using ALE distribution.
Key words :
internal wbs element number conversion_exit_konpt_output standard wbs, external project number conversion_exit_konpt_input standard wbs, internal project number conversion_exit_konps_output standard wbs, external wbs element number conversion_exit_wildc_input converts, internal wbs element number conversion_exit_konpr_output converts, ddic field prps-pspnr, external wbs element number, internal wbs element number, respective number range object, automatically converted internal number
Related Notes :
| 553832 | FAQ 2: Conversion |
| 553661 | FAQ 2: Coding masks |
| 521625 | Apparent inconsistencies during the creation of projects |
| 521483 | Input help displayed incorrectly |
| 520944 | Problems when/after creating/transporting editing masks |
| 494487 | Project System: Consulting notes |
| 453280 | Conflicting coding mask and project/WBS element |