RHMOVE30 – How to Transport Org Data Entries in SAP CRM

You might already have observed that Org Data changes ( PPOCA_CRM ) does not produce Transport requests. So, how do we move them across different systems in the landscape ?

SAP Provides a special report for this called RHMOVE30. Goto SE38 and execute the program RHMOVE30 OR use the transaction code RE_RHMOVE30
wpid-PastedGraphic1-2012-02-5-12-42.tiff

Precautions to be taken :

  1. You can either choose Org Objects or Positions. So essentially you have to create 2 transports – Org IDs first and Positions next. Always ensure that you move Org Objects first ( in a separate transport ) and Positions Objects ( Object Type = ’S’ ) in a separate transport.
  2. You can choose to transport all Org IDs or selectively choose to send ONLY some org IDs ( or position IDs ) . This can be done using the Object ID field.
  3. You can also choose to select Org Elements in the source & Target system by clicking on the “Delete Objects” flag in the Transport Section (as shown in “How to generate a TR” section below ).
  4. Choose the list of object IDs to be Transported or deleted as shown below after executing the transaction and then click on the “Transport/Delete” button. However, please ensure that you do NOT delete Org IDs in the test system.
    • wpid-PastedGraphic6-2012-02-5-12-42.tiff

SAP CRM Training | SAP SD Training | SAP Training | SAP ABAP Training

How to generate a TR ?
Goto the Transport section as shown below and click on the LOV button. Here you can create your own task or select an existing TR.
wpid-PastedGraphic4-2012-02-5-12-42.tiff

Advertisements

Welcome to MacJournal!

Welcome to MacJournal 6

To get started, create a new entry by clicking on “New Entry” in the toolbar or choosing “New Entry” from the File menu. You can also drag files from the Finder in to the Sidebar or the Entries list to import them as an entry. Show the Inspector from the View menu to see settings for the current entry, journal, and document.

What’s new in version 6?

  • Modern interface
  • Browse your entries by date, tags, status, and more
  • Full-sized calendar and timeline viewing modes
  • Create books for your entries and print the exact results
  • Track word count goals and see your progress
  • Customizable icons for entries and journals
  • Lion full screen support
  • Performance improvements across the application
  • 64-bit

SAP Status Profile – A scenario from Heavy Industries

Scenario : ABC Company manufactures Power Transformers that can be used in Nuclear Power Plants. When a Customer orders the same, a number of validations needs to be performed before the order can be finally delivered. You have been given the task of creating the different SAP User Statuses. Here are the different statuses.

  • Initial
  • Initial Site Inspection Complete
  • Concrete Base Prepared
  • Pillars Erected
  • Structural Integrity Verified
  • Power Cables Verified
  • Final Inspection done.
  • Approved
  • Rejected

Configure the status profile at the sales document header level and assign it to a custom sales document type and ensure the following.

  1. The status can ONLY go from “Initial” to ” Initial Site Inspection Complete”
  2. From “Initial Site Inspection Complete” the status can go up to “Pillars Erected” or “Concrete Base prepared” but cannot go back to “Initial”
  3. From “Concrete Base Prepared”, the status can go to the status can go up to “Structural Integrity Verified” but cannot go below “Initial Site Inspection Complete”
  4. From “Pillars Erected” the status can go up to “Final Inspection done” , but cannot go below “Initial Site Inspection Complete”
  5. From “Structural Integrity Verified” the status can go up to “Final Inspection done”, but cannot go below “Initial Site Inspection Complete”
  6. From “Power Cables Verified”, the status can go up to “Final Inspection done” , but cannot go below itself
  7. From “Final Inspection done” , the status can go up to “Rejected”, but cannot go below ” Initial site inspection complete”
  8. From Approve
  9. Only if the status is “Approved”, then the sales document can be delivered and billed.
  10. If the status is either rejected or in any other status other than “Approved”, the sales document cannot be delivered or billed.

Paste all the different statuses you have created for this scenario like this – An example is shown below. ( Use SAP Multiple Copy function to copy multiple rows/columns in one shot )

Status Profile = ZJANBATC

10    Napp    Not approved    10    20    1    1
20    veri    verificattion    20    50    1    1
30    vali    validation    30    40    1    1
40    appr    approval    40    50    1    1
50    reje    rejected    20    50    1    1

SAP Status Profile Customization for a Legal GSA based workflow

Scenario : A company sells bio-chemical equipment and has entered into an Agreement with the Government ( GSA ) whereby, they will sell to all government enterprises at a reduced price. In return, all government agencies will have to buy that kind of bio-chemical equipment from this company. As part of the GSA agreement, the company is prohibited from selling to other customers at a price lower than quoted for government customers. So, the company has set up a dedicate person in the legal department to ensure that all orders > 100,000 US $ in value should be manually verified for the prices to ensure that they are not being sold at a price that is less than that the GSA price list. The task of creating this has been given to you ( SAP SD Consultant ) . The different statuses are as follows.

  • Initial
  • Legal Dept. Approved
  • Legal Dept. Rejected

Configure a status profile at the sales document header level , assign it to a custom sales document type and ensure the following.

  1. The sales document goes to the Initial status as soon as it is created.
  2. If the document is approved, then deliveries can be performed for the order.
  3. If the document is rejected, then no further steps can be performed on the order.

Relationship between Program an Transaction code in sap

Problem : Some SAP Training students have questions on how to find out the transaction codes for some transactions in SPRO. Some students have asked questions about the direct relationship between the transaction code and abap program associated with it. Also, as part of the SAP Live Project, in order to debug certain user exits the associated program needed to be known.

solution : Typically, very few transactions under SPRO ( Customizing ) are remembered. And most of the times transaction codes do NOT exist for customizing transactions. If you look at the SAP GUI Navigation video, you would have observed that the transaction code and program are available in the bottom right corner. For example, for a Sales Order Create transaction, the program is SAP MV45A and tcode is [VA01] and

AS discussed in the SAP GUI class, a transaction code is just a shortcut to execute an “executable” program. In order to find out the mapping between the transaction code and the program, go to tcode [SE93] and enter the name of the Transaction code to find out the name of the program.

Enter the Transaction code as shown below and click on display.

The associated program will be displayed.

On the contrary if you want to find out the t-code associated with the program, there are a couple of methods ( Like SE80 and then where used etc ). The easiest method is to go to the database table TSTC. Enter the name of the Program and hit execute. ( SAP Data Browser )

The associated transaction code ( if any ) will be displayed. As you can see, there are many transaction codes associated with the program SAP MV45A depending on the screen that is being called and the mode in which it is called.

Some examples in SD configuration transactions that are commonly referred by SAP consultants in real life are as follows.

[VOK0]  – Pricing Overview
[VOPAN] – SAP Partner Determination
[VOK2] – Output Overview
[VOTXN] – SAP Text Determination
[V/05] – Display Pricing Condition Tables
[V/06] – SAP Pricing Condition Types
[V/07] – SAP Pricing Access Sequences
[V/08] – SAP Pricing Procedure
[VKOA] – SAP Account Determination

Exercises

1. List out the Program associated with Delivery Creation Transaction

2. List out the program associated with PGI Reversal

3. List out the transaction code associated with the program SAPMV80Z

4. List ouf some of the transaction codes associated with the program SAPMV50A