To effectively address the issue with the parameterization and mapping of customer numbers from the purpose of use, I recommend reviewing certain aspects of the setup in your SAP system and adjusting it if necessary. Here are some steps and considerations you should take into account: ### 1. Review the search pattern It seems like your current search pattern is basically working, but there may be a detail that was overlooked in the implementation or integration into the posting logic. Ensure that the search pattern is correctly defined to capture the desired parts of the purpose. Your current pattern: - (^|?)250###(^|$) This pattern appears to be designed to capture a four-digit number, where 250### indicates that you want to capture a specific series of numbers (250 followed by three more digits). Check that the question mark in your pattern (?) is used correctly, as in regular expressions it indicates that the previous character or group is considered optional. This could be the cause of the non-recognition in your case. ### 2. Mapping adjustment The mapping from 250### to 750### seems logical, however you report that a '*' is displayed as the debtor number. This could indicate that there is an error in the mapping or in the interpretation of the mapping. Check: - Mapping base: The base should be correctly set to the recognized values from the search pattern or another relevant source - No duplicate use of mapping and base: If you use the same values in the mapping base as in the mapping itself, this could lead to conflicts. The base should refer to the original data found in the purpose ### 3. booking rules and GVC settings - GVC 108: Ensure that the configuration of this business transaction code (GVC) is correct and that it is correctly aligned with the purpose interpretation and mapping - Posting rule: Verify that the associated posting rule is correctly associated with posting key "05" and account category "person account" ### 4. Test and Simulation - Perform further testing and simulation to see how the processing reacts with different inputs from the purpose of use. Check whether the original and the mapped customer number are displayed and processed correctly in the simulation ### Conclusion It is possible that a fine adjustment is required either in the area of the regular expressions of the search pattern or in the area of the mapping or the mapping base. Also check whether any restrictions or special features in the SAP version or in the specific settings of your SAP system need to be taken into account.
Need more help from our chatbot? Click here and visit our AI SAP Helper on the SAP learning platform et.training.1
1. log in with your Espresso Tutorials account. Digital subscription or trial access required.
