Kontakt

Ansicht
Dokumentation

RCOD_CREATE_CONNECTIVITY_SIMPL - Program RCOD_CREATE_CONNECTIVITY_SIMPL

RCOD_CREATE_CONNECTIVITY_SIMPL - Program RCOD_CREATE_CONNECTIVITY_SIMPL

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report generates the following communication settings required for the integration of S4 HANA with SAP Cloud for Customer:

  • RFC destinations to connect to the middleware i.e., SAP PI or SAP Cloud Platform Integration.
  • ALE ports for the RFC destinations.
  • Outbound ALE partner profiles for the ALE ports for all selected IDocs.
  • ALE distribution model entries for all selected IDocs.
  • Inbound ALE partner profiles for all selected IDocs.
  • Endpoints for all selected the web services.
  • Report variants for periodical reports that is executed in a batch.
  • Periodic batch jobs using the report variants for periodic IDoc outbound and inbound processing.
  • Logical ports for outbound web services.
  • Adding inbound IDocs to allowed list if the middleware is SAP Cloud Platform Integration (Note 1560878).

The report generates these settings based on some input parameters that the user enters in the different steps. Details follow.

The report creates an application log with all details of the generation that is displayed as the report output.

This report ONLY supports the creation of entities. Updates and deletions are NOT done automatically. The report doesn't change any EXISTING setting. This means that whenever you have to update information you will need to maintain those manually.

Prerequisites

A logical system id has been created in the S4 HANA system for the target SAP Cloud for Customer system. The logical system ID needs to be obtained from the communication arrangements in the SAP Cloud for Customer tenant. This is described in the guide: Prepackaged Integration with S4 HANA.

Generating the web service endpoints requires the availability of the profile DEFAULT_PROFILE, which has to be maintained in transaction SOAMANAGER. You can maintain this profile under "Technical Configuration" --> "Profile Management" (terminology might differ from release to release). It contains information about the logon procedure and access information, e.g. the protocol.

Please maintain the ALE distribution model for the receiving C4C system with the appropriate filters BEFORE executing this report. This report will generate released batch jobs that send over data to C4C. In case no ALE distribution model is maintained superfluous data may be created in C4C.

Procedure

Step 1 of 5/6 - Middleware Selection

Select the middleware you are going to use in your integration scenario. Depending on this you will have to provide different information in step 4.

Step 2 of 5/6 - Scoping Selection

Choose your desired integration scope. The questions here correspond to the business configuration scoping in your SAP Cloud for Customer tenant. Please mark the same check boxes here as you did in your SAP Cloud for Customer tenant.

Based on the selections the communication settings for the corresponding IDoc resp. Enterprise Service settings are done.

Remark

The report generates entries in the ALE distribution model for each of the IDocs mentioned here. There are no filter objects set. This means that IDocs are sent to C4C for ALL objects in the system. In most cases you may want to set filters to only send IDocs that are relevant for C4C. This has to be done manually after running this report in transaction BD64.

The following IDocs/service interfaces are generated according to the selected settings:

  • Organization Structure:
  • Outbound IDoc: COD_ERP_SD_ORGS_SAVE

  • Business Partner and Relationship:
  • Inbound Service interface: BUSINESSPARTNERSUITEBULKREPLIC, BUSINESSPARTNERRELATIONSHIPSUI, BUSINESSPARTNERSUITEBULKREPLI1, BUSINESSPARTNERRELATIONSHIPSU1

  • Outbound Service interface: CO_MDG_BP_RPLCTRQ, CO_MDG_BP_RELATIONSHIP_OUT, CO_MDG_BP_RPLCTCO, CO_MDG_BP_RELATIONSHIP_CNF_OUT

  • Business Partner End of purpose:
  • Outbound Service interface: CO_ABABUSINESS_PARTNER_EOPREMO, CO_ABABUSINESS_PARTNER_EOPCOMP, CO_BPC_CUST_ERP_EOP_CHECK, CO_BPC_CUSTOMER_ERP_EOP_BLOCK

  • Account hierarchy:
  • Outbound IDoc: COD_CUSTHIERMAS

  • Employee:
  • Outbound IDoc: HRMD_A_CFS

  • Product:
  • Outbound Service interface: CO_MDM_PRD_BULK_REPL_REQ_OUT

  • Inbound Service interface: PRODUCTMDMBULKREPLICATEREQUEST

  • Opportunity follow-up:
  • Inbound IDoc: SALESORDER_CREATEFROMDAT2

  • Inbound Service interface: COD_ERP_GET_DOC_FLOW, SALESDOCUMENTPRINTPREVIEWQUERY, ECC_SALESORDER009QR, ECC_CUSTOMERQUOTE006QR

  • Outbound IDoc: COD_OPPT_CONF

  • Opportunity pricing:
  • Inbound Service interface: COD_SALESORDER_SIMULATE

  • Sales quotes follow up:
  • Inbound IDoc: SALESORDER_CREATEFROMDAT2

  • Inbound Service interface: ECC_SALESORDER009QR, SALESDOCUMENTPRINTPREVIEWQUERY, COD_ERP_GET_DOC_FLOW, CUSTOMERQUOTEFOLLOWUPORDERCREA

  • Outbound IDoc: COD_OPPT_CONF

  • Outbound Service Interface: CO_COD_CUSTOMER_QUOTE_SOR_CONF

  • Sales quote pricing:
  • Inbound Service Interface: COD_SALESORDER_SIMULATE

  • Service ticket:
  • Inbound IDoc: SALESORDER_CREATEFROMDAT2, COD_SERVICE_CONFIRMATION

  • Outbound IDoc: COD_SERVICE_REQUEST_CONF

  • Service ticket follow up:
  • Outbound IDoc: COD_CONFIRM_CREATEFROMDAT

  • Inbound IDoc: COD_SERVICE_CONFIRMATION, SALESORDER_CREATEFROMDAT2

  • Exchange rates:
  • Inbound Service interface: ECC_EXCHGRATEBYER_QR

  • Sales Order:
  • Inbound IDoc: SALESORDER_CREATEFROMDAT2, COD_CONFIRM_CREATEFROMDAT

  • Outbound IDoc: COD_REPLICATE_SALES_ORDER

  • Customer Material Info:
  • ,,Outbound IDoc: COD_CUST_MAT_INFO

  • Equipment:
  • Outbound IDoc: COD_EQUIPMENT_SAVE

  • Functional Location:
  • Outbound IDoc: COD_FUNCTIONAL_LOCATION_SAVE

  • Measuring Point:
  • Outbound IDoc: COD_MEASURING_POINT_SAVE

  • Measurement Document:
  • Outbound IDoc: COD_MEASUREMENT_DOC_SAVE

  • Characteristic:
  • Outbound IDoc: CHRMAS

  • Pricing condition:
  • Outbound IDoc: COND_A

  • Classes and Classifications
  • Outbound IDoc: CLFMAS, CLSMAS

  • Inbound IDoc: CLFMAS

  • Contracts
  • Outbound IDoc: COD_CONTRACT_CREATEFROM_DAT

  • Inbound IDoc: COD_CONFIRM_CREATEFROMDAT

  • ,,Outbound Service Interface: CO_SLS_CONTRACT_CALL_OFF_STATI

  • Contract Pricing
  • Inbound Service Interface: COD_CONTRACT_SIMULATE

  • Time Report
  • Inbound IDoc: COD_CATS_TIME_REPORT

  • Stock Location
  • Outbound IDoc: COD_STOCK_REPLICATE

  • Attachment (In all master and transactional data)
  • Inbound Service Interface: ATTACHMENTFOLDERREPLICATIONRE1

  • Outbound Service: CO_CODERINT_ATTACHMENT_FOLDER

Step 3 of 5/6 - General Settings

SAP Cloud for Customer System

Please select the logical system id representing the SAP Cloud for Customer tenant (see prerequisites above). If the logical system has not been created yet, you can also use the pushbutton "Create Logical System" to navigate directly to the transaction BD54.

Batch Job Settings

Here you provide the settings for the batch jobs which are created and scheduled automatically by this report.

  • The "Job Schedule Interval" gives the job period in minutes for the batch jobs.
  • The "Job User" gives the user id which will be the owner of these batch jobs.

In this case you can specify the interval in minutes and the user the batch jobs will be created for.

IDoc outbound processing batch job

This job is relevant for generating IDocs based on change pointers (report RBDMIDOC) and sending the created IDocs (report RSEOUT00). Additionally, failed outbound messages are reprocessed to clean up the TRFC queue using report RSARFCCP and RBDAGAIN.

IDoc inbound processing batch job

This job is relevant to process the received IDocs with report RBDAPP01. Additionally, with report RBDMANI2 failed inbound messages are reprocessed

Step 4 of 5/6 - Settings for Middleware

This screen is dynamically built depending on the selection of the step 1. The connection settings, you need to specify here, are used to generate the RFC destinations using the following rules:

  1. SAP Cloud Platform Integration: RFC connection of type G (HTTP Connections to External Server)
  2. SAP PI 7.1 EhP1 and above (Dual stack): RFC connection of type 3 (ABAP Connections)
  3. SAP PI 7.3 and above (Java only): RFC connection of type T (TCP/IP connections)

To select the right option, you need to ask your IT department, which middleware should be used in your scenario. If you're using "SAP PI", you also need to check the EhP level to select between the latter both options.

In the SAP PI cases it is always created exactly one RFC destination per logical system for handling the connectivity. For the SCPI case for each technical outbound interface an own RFC destination is generated.

Step 5 of 5/6 - Consumer Proxy Settings

The consumer proxy settings are relevant for scenarios, which include an outbound communication via web service, e.g. the replication of attachments. For this purpose, the corresponding logical port is generated and therefore the necessary host access data has to be maintained.

Maintain the following host access parameters based on the selection of the step 1:

  • URL access path: URL path of the middleware endpoint must be given for the following fields based on the selection of step 1 and 2. URL Access path can be fetched from the standard iFlow excel in case of SCPI and sender channel agreement in case of PI.
  • Business Partner Replication - e.g. /cxf/S4/C4C/ReplicateBusinessPartner

  • Business Partner Relationship - e.g. /cxf/S4/C4C/ReplicateBusinessPartnerRelationship

  • Business Partner Confirmation - e.g. /cxf/S4/C4C/BusinessPartnerSUITEBulkReplicateConfirmation_Out

  • Business Partner Relationship Confirmation - e.g. /cxf/S4/C4C/BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out

  • Check Business Partner End of Purpose - e.g. /cxf/S4/C4C/ABABusinessPartnerEOPRemoteOut

  • Maintain Business Partner End of Purpose - e.g. /cxf/S4/C4C/ABABusinessPartnerEOPComplout

  • Check Customer End of Purpose - e.g. /cxf/S4/C4C/CustomerERPEndOfPurposeCheckQueryResponse_Out

  • Maintain Customer End of Purpose - e.g. cxf/S4/C4C/CustomerERPEndOfPurposeBlockNotification_Out

  • Product Replication - e.g. /cxf/S4/C4C/ProductMDMBulkReplicateRequest_Out

  • Attachment Replication - e.g. /cxf/S4/COD/ReplicateCustomerOrderAttachmentFolder

  • Contract Call Off Statistics - e.g. /cxf/S4/ContractCallOffStatisticsReplicationOut

Bi-Directional Quote Follow-Up - e.g. /cxf/ERP/C4C/CustomerQuoteFollowUpOrderRequestConfirmation_Out

  • Logical Port: any arbitrary string, which serves as name for the logical port, e.g. DEF_LOGPORT
  • Computer Name: target host URL
  • URL port: target host port
  • URL protocol: target host protocol
  • Proxy settings
  • Logon procedure

Step 6 of 5/6 - Summary

This is the last screen before the connectivity settings are generated. It consists of information about what you have selected in the previous steps and should represent a short summary for you to be able to make a quick review. If you are fine with the settings you can start the generation of the needed entities by clicking the pushbutton "Generate".

After accepting the final confirmation popup all entities are generated. Existing settings are not touched. Only new entries are generated.

A Data Replication Framework (DRF) Model with ID ' $S4HTOC4C$' is generated to replicate Business Partners and Relationships. Additionally, the trigger to send Business Partner and Relationship messages from S/4HANA is activated.

Output

The report generates an application log with all details of the generation that is displayed as the report output. For example, it lists the object IDs of all generated objects.

It also shows a message if a certain setting already existed. In such a case, the setting is not updated.

The application log is stored in the database and is available after leaving the report. You can view it later in the application log viewer (transaction /nSLG1). The log object id is COD_CREA_CONN_SIMPLE.






ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 17076 Date: 20240520 Time: 124644     sap01-206 ( 186 ms )