How to use PSA52 - Rollup II - Dividir producto rollup

SAP Transaction Code - Details

• Transaction Code: PSA52

  Description: Rollup II - Dividir producto rollup

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Production Sharing Accounting > Processing > PSA Actual > Rollup II - Split Rollup-Product
  • Accounting > Production Sharing Accounting > Processing > PSA Planning > Rollup II - Split Rollup-Product

• • Program: RGPSA_ROLLUP_II

    Screen: 1000

    Authorization Object:

  • Development Package: GJPSA

    Package Description:

    Parent Package: JVA_PSA

  • Module/Component: CA-JVA

    Description: Joint Venture und Production Sharing Accounting

Smart SAP Assistant

• SAP Tcode: PSA52 - Rollup II - Dividir producto rollup

   Hierarchy
  
  Overview:
  The SAP transaction code PSA52 is used to create a product hierarchy in the Rollup II system. This hierarchy is used to organize and manage product data in the system. The hierarchy can be split into multiple levels, allowing for more detailed organization of the data. 
  
  Functionality: 
  The PSA52 transaction code allows users to create a product hierarchy in the Rollup II system. This hierarchy can be split into multiple levels, allowing for more detailed organization of the data. The hierarchy can also be used to assign different characteristics to each level, such as pricing or availability. 
  
  Step-by-step How to Use: 
  1. Log into the SAP system and enter transaction code PSA52. 
  2. Select the “Create” option from the menu. 
  3. Enter a name for the product hierarchy and select “Split Rollup-Product Hierarchy” from the drop-down menu. 
  4. Enter the desired characteristics for each level of the hierarchy and click “Save” when finished. 
  5. The product hierarchy will now be created and available for use in the Rollup II system. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with the Rollup II system before attempting to use this transaction code. Additionally, users should ensure that they have all of the necessary information before creating a product hierarchy, as it cannot be changed once it has been created.