CRM and CX Blogs by SAP
Stay up-to-date on the latest developments and product news about intelligent customer experience and CRM technologies through blog posts from SAP experts.
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member195647
Discoverer
SAP offers customers the capability to extend pre-packaged content that has been previously delivered by SAP (iflows). Extension scenarios are common when customers want to bring new fields into the Cloud application from their on-premise of altogether extend end-end from on-premise to the Cloud.
Starting from SAP Hybris Cloud for Customer 1702 release, Time Report can be replicated from C4C to ERP, so that CATS records can be created there. In this blog, we show what the required actions are, which have to be accomplished by the customers to enable extensibility.

More details about time report replication functionality can be found in the blog:

https://blogs.sap.com/2017/02/03/whats-new-in-1702-sap-hybris-cloud-for-customer-erp-integration

 

We can separate the required actions into three main points:

Actions required in C4C:
In C4C, adding new fields can be done in the header level (Time Report) or in the item level (Time Entry).
For more information about how to extend the corresponding outbound interface which is used in C4C to replicate time reports, please return to the document: How to Extend SAP Cloud for Customer -SAP On-Premise Pre-Packaged Integration Content (PI/HCI).https://archive.sap.com/documents/docs/DOC-54548

 

 

Actions required in SAP ERP:
In ERP, for each time entry received from C4C, CATS record is created in ERP.  These CATS records are stored in the table CATSDB, which we should extend in ERP. However, for the time report header itself, there is no corresponding object in CATS interface in ERP which can be created to represent time reports of C4C. Therefore, all the fields which are extended in the time report level, and we are interested in moving them to ERP, we should store them in CATSDB too.
Example: if a time report header has been extended to have one new field ZZ_H. Time entry has been extended to have two new fileds ZZ_F1 and ZZ_F2. CATSDB table has to be extended to have three fields ZZ_H, ZZ_F1 and ZZ_F2. Then, for each CATS record which is going to be created in ERP, three fields should be filled: ZZ_H, ZZ_F1 and ZZ_F2.
To extend CATSDB table, a customization include CI_CATSDB is provided in this table. The customer has to create it and add the fields to it. After activating it, the table CATSDB will be extended to include the new fields.
In the following screen shot, we see that CI_CATSDB has three fields: ZZ_H, ZZ_F1 and ZZ_F2.



 

 

Actions required in the middleware (PI/HCI):
In the middleware the message mapping COD_ERP_TimeReportReplication is used to map the C4C message to the IDoc COD_CATS_TIME_REPORT01 which is used to post time entries in ERP and create the corresponding CATS records. As shown in the following screen shot, the IDoc is structured to have a dedicated one segment E101COD_S_CATS_TIME for time report and one or several segments E101COD_S_CATS_TIME_I for time entries. In the segment of time entry, there is a sub-segment E101COD_BAPICATS7 for the extended fields by the customer.



The following screen shot shows the structure of the E101COD_BAPICATS7 segment:



In the middleware, the following points have to be taken into consideration during the mapping of the new extension fields:

  • Each new extension field in the time entry level has to be mapped to the extension segment in IDoc.

  • Each new extension field in the time report level has to be mapped and copied to the all extension segments of all time entries of the current time report.

  • APPL_SNAME: It should not be mapped by the customer.

  • VALUEPART1:

    • Keep the first 10 characters empty.

    • Respect the sequence of the custom fields defined in ERP in the structure CI_CATSDB from the CATSDB table.

    • Respect the data length of each field defined above.



  • VALUEPART2, VALUEPART2 and VALUEPART4:

    • Respect the sequence of the custom fields defined in ERP in the structure CI_CATSDB from the CATSDB table.

    • Respect the data length of each field defined above.



  • The total length of all extension fields should not be more than 950 characters.