batch management

3
5/19/2018 BatchManagement-slidepdf.com http://slidepdf.com/reader/full/batch-management-56195546d23f0 1/3 SAP Note Header Data Symptom As of CRM Release 4.0 it is possible to enter batches or batch characteristics in the order. Beforehand, data of the classification must be replicated into the CRM server. Other Terms Batches, batch characteristics, classification, OBJCL, CLASS, ATTRIBUTE Reason and Prerequisites ¡ The leading system for the master data of the classification is the R/3 system (as of Release 4.6B). The R/3 system must also be the source system of products to be handled in batches. ¡ You can use function module CLIDL_LOAD_CUSTOMIZING to transfer the Customizing settings of the classification between the R/3 system and the CRM server. In this case, you should limit the transfer to class type 023. Caution: Function module CLIDL_LOAD_CUSTOMIZING is designed for a one-time transfer of the Customizing data. A multiple application of the function module (for example, in order to replicate changes in R/3 Customizing) is not possible. You have to implement such changes manually in the CRM server. Also refer to the documentation of the function module. ¡ An automatic synchronization of the Customizing settings does not occur. In case of changes in the R/3 system, you have to implement these changes manually in the CRM server. ¡ Objects CLASS, ATTRIBUTE, and OBJCL are used for the data exchange of the master data. It is absolutely necessary that the initial download of objects CLASS, ATTRIBUTE and OBJCL occurs before object MATERIAL is downloaded. ¡ Customizing table TBE31 of the R/3 system must contain the following entries: EVENT APPLK FUNCT 00004000 BC-MID CRS_CHARACT_COLLECT_DATA 00004001 BC-MID CRS_CLASS_COLLECT_DATA 00004002 BC-MID CRS_OBJCL_COLLECT_DATA_NEW ¡ You must assign product set type COMM_PR_BATCH to the material type that includes materials to be handled in batches. Use Transaction COMM_HIERARCHY to assign the product set type. In this transaction, select hierarchy R3PRODSTYP and product subtypes MAT_. Assign set type COMM_PR_BATCH to the required material types. ¡ In Customizing table SMOFPARSFA of the CRM server, the following parameter must be maintained: PARSFAKEY PARNAME PARVAL1 R3A_COMMON CRM_DEFAULT_DESTINATION R/3 destination (->SM59) Solution Consider the prerequisites listed above. Validity 618191 - R/3 data exchange of classification data (class type 23)  Version 5 Validity:  04.06.2004 - active Language English Released On 07.06.2004 18:02:01 Release Status Released for Customer Component CRM-MD-PRO-IF-PRO Data Exchange Products Priority Recommendations / Additional Info Category Installation information Software Component From Rel. To Rel. And Subsequent BBPCRM  400  400  

Upload: anant-srikrishna

Post on 10-Oct-2015

10 views

Category:

Documents


0 download

DESCRIPTION

Batch Management

TRANSCRIPT

  • SAP Note

    Header Data

    Symptom

    As of CRM Release 4.0 it is possible to enter batches or batch characteristics in the order. Beforehand, data of the classification must be replicated into the CRM server.

    Other Terms

    Batches, batch characteristics, classification, OBJCL, CLASS, ATTRIBUTE

    Reason and Prerequisites

    The leading system for the master data of the classification is the R/3 system (as of Release 4.6B). The R/3 system must also be the source system of products to be handled in batches.

    You can use function module CLIDL_LOAD_CUSTOMIZING to transfer the Customizing settings of the classification between the R/3 system and the CRM server.

    In this case, you should limit the transfer to class type 023. Caution: Function module CLIDL_LOAD_CUSTOMIZING is designed for a one-time transfer of the Customizing data. A multiple application of the function module (for example, in order to replicate changes in R/3 Customizing) is not possible. You have to implement such changes manually in the CRM server. Also refer to the documentation of the function module.

    An automatic synchronization of the Customizing settings does not occur. In case of changes in the R/3 system, you have to implement these changes manually in the CRM server.

    Objects CLASS, ATTRIBUTE, and OBJCL are used for the data exchange of the master data.

    It is absolutely necessary that the initial download of objects CLASS, ATTRIBUTE and OBJCL occurs before object MATERIAL is downloaded.

    Customizing table TBE31 of the R/3 system must contain the following entries:

    EVENTAPPLKFUNCT 00004000BC-MIDCRS_CHARACT_COLLECT_DATA 00004001BC-MIDCRS_CLASS_COLLECT_DATA 00004002BC-MID CRS_OBJCL_COLLECT_DATA_NEW

    You must assign product set type COMM_PR_BATCH to the material type that includes materials to be handled in batches. Use Transaction COMM_HIERARCHY to assign the product set type. In this transaction, select hierarchy R3PRODSTYP and product subtypes MAT_. Assign set type COMM_PR_BATCH to the required material types.

    In Customizing table SMOFPARSFA of the CRM server, the following parameter must be maintained:

    PARSFAKEYPARNAMEPARVAL1 R3A_COMMONCRM_DEFAULT_DESTINATION R/3 destination (->SM59)

    Solution

    Consider the prerequisites listed above.

    Validity

    618191 - R/3 data exchange of classification data (class type 23)

    Version 5 Validity: 04.06.2004 - active Language English

    Released On 07.06.2004 18:02:01 Release Status Released for Customer Component CRM-MD-PRO-IF-PRO Data Exchange Products Priority Recommendations / Additional Info Category Installation information

    Software Component From Rel. To Rel. And Subsequent

    BBPCRM 400 400

  • Support Packages & Patches

    References

    This document refers to:

    SAP Notes

    This document is referenced by:

    SAP Notes (2)

    500 500

    Support Packages

    Software Component Release Support Package

    BBPCRM 400 SAPKU40001

    856825 Checks and FAQs for LeanBatches 716233 Error in CLIDL_LOAD_CUSTOMIZING

    856825 Checks and FAQs for LeanBatches 716233 Error in CLIDL_LOAD_CUSTOMIZING