As SAP Expert has already emphasised several times, aligning objects in different SAP systems is a very important part of the multi-system landscape maintenance.
We have discussed the fact that the transport system is the most usual way to move configuration changes throughout the landscape, and how you can align certain master data.
However, some objects in SAP require “special treatment” when moving them across. One of them is tax code, and you can read about the process of moving Tax Codes and Substitutions / Validations across the landscape.
Today we will discuss another “special treatment” object – number range.
Number range is an object in SAP that is assigned to another object that requires automatic or manual numbering. A good example is document number range. You specify different document types, and assign number ranges to them. Then you need to maintain number ranges separately – assigning lower and upper limit of each of them, splitting by company code, year and assigning other parameters. You have an option to edit “status” of number range too – the last used number for automatic numbering. Opposite to many other configuration objects, you will not be asked for a transport request for number range when saving data in Development system. It means that you have 2 options to maintain number range:
Do it separately in each client. You may need additional authorisations for that.
Include number ranges in the transport request in Development system and move across the landscape.
You need to decide yourself, based on your project needs and approaches, what is the best option for you. If you decide to use transport requests, SAP Expert can give you some recommendations.
To include number ranges in the Transport Request, please use menu Interval – Transport to include number ranges in the Transport Request. You may get additional questions, depending on the object you are going to transfer. Please read them carefully and act accordingly.
Include Number Ranges in a separate Transport Request, and mark it as “move once only” in the text. Of course, you must move the transport request only once in each client. This is because SAP removes existing number ranges, including their statuses, in the target system before importing the transport request. If your target system already has some documents, the status of the number range will not be the same as stored in the transport request. Re-importing the number range from transport request will change the status. This will most likely block the process of new document posting. Of course, this can be solved by manual editing of the status in the target client, but it is way better not to create the problem initially. So, “move once only!!!”
Next time we will talk about other objects with “special treatment”.
Share the knowledgeFacebookGoogle+TwitterLinkedinDiggemailPeriod closing is a process that involves many steps in different SAP modules. Even if we take SAP Finance (FI) alone, period closing activities include various steps in GL, AP, AR, Assets and other submodules. To ensure the period closing is complete and reports are finalized, users maintain a table with periods open […]
Share the knowledgeFacebookGoogle+TwitterLinkedinDiggemailMy dear readers! I believe the majority of you work in SAP world. Some of you have just started, some of you work with SAP all your life. But do you actually remember how your SAP life stared? What was your first project? What was your first task? Let us share the experience, […]