Settings to Generate Transport Request for a Table

The document explains you, how to generate a transport request manually, when you do a configuration but system doesn’t generates you a transport request.

Example: I was trying to cancel an excise invoice in transaction code J1IEX but it was throwing an error message, saying ‘Please Maintain the Rejection Code’ but there were no rejection codes available in the F4 option. In order to resolve the issue I’ve configured the same in path: SPRO – Logistics – General – Tax on Goods Movements – India – Business Transactions – Maintain Rejection Codesbut when was done with configuration, the system was not generating a transport request automatically!!!. The result, I couldn’t able to move the changes to neither QAS nor PRD systems from DEV system.

Solution:

Please find the below steps to resolve the issue.

• Go to transaction SE11. Open table J_1IREJMAS

• On the menu bar, go to “Utilities -> Table Maintenance Generator”

• In the block for ‘Dialog Data Transport details’, for the option ‘Recording Routine’, select the radio button ‘Standard recording Routine‘ instead ‘no, or user, recording routine’

• Before

          

• After

      

• Ensure that the Authorization Groups has ‘w/o auth. group’ entered.  Authorization Group should be &NC&

• While on this screen, save and go to the menu bar, “Environment -> Maintenance Objects -> Change.

• In the ‘object attributes’ block, for the transport option, select ‘Automatic Transport‘ instead‘No transport’

Before

     

After

            

• Click the icon “Adjust to Dict.’ this will adjust your object category.

• Click the ‘Check Consistency’ icon. This will check for the Completeness of the maintenance view.

• Once the consistency check is through, save.
• Come back to the table structure (using backward navigation) and reactivate the table, if required (under normal circumstances, this should not be required).

The same is applicable for ZTABLE also.

Number of ways to display the messages

Number of ways to display the messages.
1). MESSAGE 'abs' type 'I'.

2). MESSAGE I002 (<Message Class>)
            In the message class we have to write the corresponding message for 002.

3). REPORT <Program Name> MESSAGE-ID <Message Class>.
        MESSAGE I002.
            In the message class we have to write the corresponding message for 002.

4). MESSAGE i006 WITH text-003.
                    In the text symbols 003 we have to write the corresponding message.

5). MESSAGE text-001 type 'I'.
                        In the text symbols 001 we have to write the corresponding message.

6). MESSAGE i006 WITH 'Invalid purchase order Number'(003).
       006 message description is sending at runtime, in the message class we mention & & & & for the corresponding 006 number. In the text symbols 003 we are writing the description, it    just for our display purpose.

7). MESSAGE ID '<Message Class>' type 'I' NUMBER 002.

8). MESSAGE i003 (<Message Class>) WITH '<Some text message> '.

9). MESSAGE i003 (<Message Class>) WITH text-003.
                        In the text symbols 003 we have to write the corresponding message.

10). MESSAGE i003 (<Message Class>) with p_user.
                        Only for that particular user can get the message.