INCLUDE ARBCIG_ORDER_REQUEST_002 IF FOUND.

But…what happens when you want to send the PDF of the purchase order, and this PDF is generated in a SAPScript form, that is executed inside the output type message:

This Output type is configured in NACE transaction where you enter the form name of the SAPScript that will be triggered:

The complication of this functionality is that this printout of the purchase order, is triggered when the output message is already processed and the purchase order is already approved, but when you are sending the purchase order to Ariba Business Network, this steps are not finished yet, so you must implement a logic to print the PDF of the purchase order, executing manually the SAPScript in real time when the PO is sent to Business Network.

We can do that implementing the BADI ARBCIG_BADI_ATTACHMENT_UTIL where we process the attachments of the PO.

We only need the method PRE_ATTACHMENT_PROCESS:

Inside this method, we will implement the next logic:

1. Search in NAST table with the PO ID if exists the message you are configured in NACE transaction for the purchase order you are approving.
   
2. Read the data of the PO from MF ME_READ_PO_FOR_PRINTING.
   
3. Execute the MF ECP_PRINT_PO with the form ID.
   
4. Read the OTF data of the form with MF READ_OTF_FROM_MEMORY.
   
5. Convert OTF data to PDF with MF CONVERT_OTF.
   
6. Encrypt the PDF from Hexadecimal to Base64 with MF SCMS_BASE64_ENCODE_STR.
   
7. Complete the E1ARBCIG_ATTACH_HDR_DET segment with header data of attachment.
   
8. Complete the E1ARBCIG_ATTACH_CONTENT_DET segment with the content of Base64 string.

All this steps are detailed in the next code:

method IF_ARBCIG_ATTACHMENT_UTIL~PRE_ATTACHMENT_PROCESS.


    DATA: gint_nast      TYPE nast,
          lv_count       TYPE i,
          lv_ebeln       TYPE ebeln,
          ent_screen     TYPE c,
          ent_retco      TYPE i,
          l_nast         TYPE nast,
          l_druvo        TYPE t166k-druvo,
          l_from_memory,
          toa_dara       TYPE toa_dara,
          arc_params     TYPE arc_params,
          aux_form       TYPE tnapr-fonam VALUE 'ZMMSS_PEDCOMPRAS',
          lv_message     TYPE tnapr-fonam VALUE 'ZPC',
          lt_docs        TYPE TABLE OF docs,
          l_doc          TYPE meein_purchase_doc_print,
          otf            TYPE TABLE OF itcoo,
          pdf_bytecount  TYPE i,
          nom_archivo    TYPE string,
          pdfout         TYPE TABLE OF tline,
          lv_debug       TYPE char1,
          pdf            TYPE XSTRING,
          ls_e1edk01     TYPE e1edk01,
          ls_hdr_det     TYPE E1ARBCIG_ATTACH_HDR_DET,
          ls_hdr_content TYPE E1ARBCIG_ATTACH_CONTENT_DET,
          idoc_data      TYPE edidd,
          lv_base64      TYPE string,
          len            TYPE i,
          lv_offset_mx   TYPE i,
          lv_offset_mn   TYPE i,
          div            TYPE i,
          temp           TYPE i.

*"---------------------------------------------------------------------
*" NOTES:
*"  1) Control display of PO in GUI window
*"       ENT_SCREEN = 'X'   => PO is displayed in GUI window
*"       ENT_SCREEN = space => Spool file of the PO is created
*"                               Spool number is returned in message
*"  2) Write PO to memory as OTF
*"       NAST-SORT1 = 'SWP' => PO is written to memory as OTF
*"                               Memory ID = PO Number - Use function
*"                               READ_OTF_FROM_MEMORY to retrieve
*"       NAST-SORT1 = space => PO is NOT written to memory
*"---------------------------------------------------------------------

*Infinite LOOP only for debug
    SELECT SINGLE low
    FROM ARBCIG_TVARV
    WHERE name = 'DEBUG_PRE_ATTACHMENT_PROCESS'
    INTO @lv_debug.

    IF lv_debug EQ 'X'.
      WHILE lv_debug IS NOT INITIAL.
      ENDWHILE.
    ENDIF.

*First we obtain the PO ID from field
*Belnr from segment e1edk01
    READ TABLE c_edidd[] INTO idoc_data INDEX 1.
    CHECK idoc_data-segnam EQ 'E1EDK01'.
    MOVE idoc_data-sdata TO ls_e1edk01.

    lv_ebeln = ls_e1edk01-belnr.

    IF lv_ebeln IS NOT INITIAL.

*Field lv_message is the output type message where the form is configured
      SELECT SINGLE *
         FROM nast INTO gint_nast WHERE objky EQ lv_ebeln
          AND kschl EQ lv_message.

*We ensure the output type exists for the PO.
      CHECK sy-subrc EQ 0.

      gint_nast-sort1 = 'SWP'.

      IF gint_nast-aende EQ space.
        l_druvo = '1'.
      ELSE.
        l_druvo = '2'.
      ENDIF.

      CLEAR ent_retco.

      CALL FUNCTION 'ME_READ_PO_FOR_PRINTING'
        EXPORTING
          IX_NAST        = gint_nast
          IX_SCREEN      = ent_screen
        IMPORTING
          EX_RETCO       = ent_retco
          DOC            = l_doc
          EX_NAST        = l_nast
        CHANGING
          CX_DRUVO       = l_druvo
          CX_FROM_MEMORY = l_from_memory.

*      CHECK ent_retco EQ 0.
      IF ent_retco EQ 3.
        "It means the PO is not released yet, but this is normal, dont panic.
        
        CLEAR ent_retco.
      ENDIF.

      CHECK ent_retco EQ 0.

*Field aux_form is the SAPScript ID form.
      CALL FUNCTION 'ECP_PRINT_PO'
        EXPORTING
          IX_NAST        = l_nast
          IX_DRUVO       = l_druvo
          DOC            = l_doc
          IX_SCREEN      = ent_screen
*         IX_XFZ         =
*         IX_MFLAG       = ' '
          IX_FROM_MEMORY = l_from_memory
          IX_TOA_DARA    = toa_dara
          IX_ARC_PARAMS  = arc_params
          IX_FONAM       = aux_form
        IMPORTING
          EX_RETCO       = ent_retco.

      CLEAR otf.

      CALL FUNCTION 'READ_OTF_FROM_MEMORY'
        EXPORTING
          MEMORY_KEY = l_nast-objky " PO Number
        TABLES
          OTF        = otf
*       EXCEPTIONS
*         MEMORY_EMPTY       = 1
*         OTHERS     = 2
        .
      IF sy-subrc <> 0.
*        RAISE otf_error.
      ENDIF.

*We transform OTF to PDF
      CALL FUNCTION 'CONVERT_OTF'
        EXPORTING
          format                = 'PDF'
        IMPORTING
          bin_filesize          = pdf_bytecount
          BIN_FILE              = PDF
        TABLES
          otf                   = otf
          lines                 = pdfout
        EXCEPTIONS
          err_max_linewidth     = 1
          err_format            = 2
          err_conv_not_possible = 3
          OTHERS                = 4.
      IF sy-subrc <> 0.
*        RAISE error.  " oops
      ENDIF.

*We transform the PDF from Hexa to Base64
      CHECK PDF IS NOT INITIAL.

      CALL FUNCTION 'SCMS_BASE64_ENCODE_STR'
        EXPORTING
          INPUT  = PDF
        IMPORTING
          OUTPUT = lv_base64.

*If all its OK, we already have the PDF in Base64
      CHECK lv_base64 IS NOT INITIAL.

      CLEAR idoc_data.
*We insert segment E1ARBCIG_ATTACH_HDR_DET.
      idoc_data-segnam = 'E1ARBCIG_ATTACH_HDR_DET'.
      CONCATENATE lv_ebeln  '.pdf' INTO ls_hdr_det-filename.
      ls_hdr_det-charset = 'UTF-8'.
      ls_hdr_det-contentid = '1'.
      ls_hdr_det-contenttype = 'application/pdf'.
      ls_hdr_det-contentlength = pdf_bytecount.
      CONDENSE ls_hdr_det-contentlength NO-GAPS.
      MOVE ls_hdr_det TO idoc_data-sdata.
      APPEND idoc_data TO c_edidd[].

*We insert segments E1ARBCIG_ATTACH_CONTENT_DET.
      CLEAR idoc_data.
      idoc_data-segnam = 'E1ARBCIG_ATTACH_CONTENT_DET'.
      len = strlen( lv_base64 ).
      lv_offset_mx = 255.
      lv_offset_mn = 0.
      div = ceil( len / 255 ).
      do div times.
        clear ls_hdr_content.
        IF lv_offset_mn GE len.
          "Last loop
          EXIT.
        ELSE.
          temp = len - lv_offset_mn.
          IF temp LT lv_offset_mx.
          "Last loop
            ls_hdr_content-content = lv_base64+lv_offset_mn(temp).
            MOVE ls_hdr_content TO idoc_data-sdata.
            APPEND idoc_data TO c_edidd[].
            EXIT.
          ENDIF.
          ls_hdr_content-content = lv_base64+lv_offset_mn(lv_offset_mx).
          MOVE ls_hdr_content TO idoc_data-sdata.
          APPEND idoc_data TO c_edidd[].
          lv_offset_mn = lv_offset_mn + lv_offset_mx.
        ENDIF.
      enddo.

    ENDIF.

  endmethod.

Summary

As a final result, the buyer will only add the message output type in the purchase order, without need of attaching anything to the purchase order, and the system automatically will print this PDF in background and will be attached this PDF to the IDOC sent to business network.

And finally, the supplier will have the PDF inside the purchase order in business network:

The post Send SAPscript form PDF from output type message to Business Network appeared first on ERP Q&A.

SAP Analytics Cloud makes it easy for businesses to understand their data through its stories, dashboards and analytical applications. However, sometimes we might not be sure how we can leverage SAC to create these based on data from other applications

For this worked example, we’re going to make use of SAP Data Intelligence Cloud to retrieve data from SAP Ariba through its APIs, before storing it in SAP HANA Cloud’s JSON Document Store

In further blog posts, we will build a model on top of this stored data and show how this can be consumed in an SAP Analytics Cloud Story. The focus of this series of blog posts is to show a technical approach to this need, not to provide a turnkey ready-to-run SAC story. After following this series you should have an understanding of how you can prepare your own stories using this approach

Ariba Analytics in SAP Analytics Cloud

For this example, we’re going to create a simple story that lets you know how much spend has been approved within Ariba Requisitions created in the last thirty days

A Requisition is the approvable document created when a request is made to purchase goods or services. Our approach will let us view only the Approved Requisitions, excluding those still awaiting approval

For those feeling more adventurous, this setup can be repeated with different document types, and those combined to create more in depth SAP Analytics Cloud Stories. This is outside of the scope of our blog series

Solution Overview

Our finished solution will need SAP HANA runtime artifacts such as Document Store Collections, SQL Views and Calculation Views. We will define these as design-time artifacts in Business Application Studio, then deploy them to an HDI Container within our SAP HANA Cloud instance

Using a scheduled SAP Data Intelligence Cloud Pipeline, we’ll query SAP Ariba’s APIs and place the data within our HANA Cloud Document Store Collection

Our SQL View lets us create a view on top of the data within our JSON Documents. Creating a Calculation View on top of one or many SQL views will let us expose the data to SAP Analytics Cloud

SAP Analytics Cloud can use HANA Cloud Calculation Views as the source for Live Data Models. With Live Data Models, data is stored in HANA Cloud and isn’t copied to SAP Analytics Cloud

This gives us two main benefits: We avoid unnecessarily duplicating the data, and ensure changes in the source data are available immediately (provided no structural changes are made)

Finally, we use the Live Data Model to create a Story within SAP Analytics Cloud. Once we’ve got everything set up, we can use this story to check our data at any time, with the Data Intelligence Pipeline refreshing the data in the background on a predefined schedule

Creating an Ariba Application

In order to access the APIs provided by Ariba, we’ll need to have what’s known as an Ariba Application. We do this through the SAP Ariba Developer Portal

For our use case we will be requesting access to the Operational Reporting for Procurement API

Once the Application has been created, we’ll need to request API access for the Application

Once the API Access Request has been approved by Ariba, your admin will be able to generate the OAuth Secret for our application

This will generate our OAuth Secret, which is required to use the API. The secret will only be displayed once, so the admin should (securely) store this and provide it to you for use in the application

If the OAuth Secret is lost, the admin can regenerate it, at which point the old secret will stop working and you will have to use the newly generated secret

Ariba API

When we call the Ariba API, we have a number of things to consider. For our example, we’re using the Synchronous API to retrieve data, but there’s also a set of Asynchronous APIs you should consider when retrieving bulk data

In addition, when retrieving data sets, you have to specify an Ariba View that you wish to retrieve. These are similar to reporting facts in the Ariba solution, such as Requisition or Invoice. Views will specify which fields are returned, and may also specify filters you should provide when calling them

To simplify our example we’re going to use a System View, which is predefined in Ariba. You are also able to work with Custom Views using the View Management API to better match your requirements but this falls outside the scope of this blog series

To explore these at your own pace, you can visit developer.ariba.com

Enabling Document Store in HANA Cloud

The Document Store is SAP HANA Cloud‘s solution for storing JSON Documents. While the Column and Row Stores use Tables to store their data, the Document Store stores data inside Collections

Before we activate the Document Store in HANA Cloud, just a word about resources. Like the Script Server, the Document Store is an additional feature that can be enabled, however we should consider HANA Cloud’s current resourcing before enabling it.

When we’re ready to enable, we’ll need to navigate to SAP HANA Cloud Central.

From HANA Cloud Central, we can then activate the Document Store

Once our HANA Cloud instance has restarted, we’ll be able to use the Document Store

Creating a DocStore Collection in Business Application Studio

While we can create a Collection directly using SQL through Database Explorer, we want to make sure we also have a design-time artifact for our DocStore Collection

To do this, we’ll use the Business Application Studio. For those unfamiliar with Business Application Studio, you can follow this Learning Journey Lesson to set up a Workspace – we’ll assume this is already in place

It’s time to set up our SAP HANA Database Project, and create the HDI Container where our runtime objects will reside

Next we’ll need to provide some information for our project

Double check the Database Version and Binding settings then click Next

Next we have to bind the project to a HANA Cloud instance within Cloud Foundry. The Endpoint should be automatically filled, but we have to provide our Email and Password before we can perform the binding

For this example we’re going to create a new HDI Container

If our Cloud Foundry space has more than one HANA Cloud instance, we may want to disable the default selection and manually choose the HANA Cloud instance where our container will reside

Now that we have our HDI Container and SAP HANA Project set up, it’s time to create our design-time objects. First, we login to Cloud Foundry

Next, we’ll create our DocStore Collection

After the deployment is successful, we have both our design-time .hdbcollection artifact, as well as the runtime DocStore collection which has been created in our HDI Container

Creating our Connections in Data Intelligence

So far we’ve gained access to Ariba APIs and enabled the Document Store in our HANA Cloud Instance. Next, we’ll be setting up two Connections in Data Intelligence Cloud

The first Connection will allow our Data Intelligence Pipeline to query the Ariba APIs to retrieve our data, and the second will allow us to store this data in the Document Store within our HDI Container

First, we use the DI Connection Manager to create a new Connection, selecting OPENAPI as the Connection Type

Our OpenAPI Connection will be used to send the request to Ariba. We’re going to set the connection up as below, using the credentials we received when we created our Ariba Application

Next, we’re going to create a HANA Connection that will let us work with the HDI Container we created earlier. To get the credentials, we have to go to the BTP Cockpit

We’ll want to keep this window open as we create our HANA DB Connection, as it has the details we need. Within Data Intelligence Cloud, create a new connection of type HANA_DB and fill it out as below using the credentials

While we have the credentials open, take note of the Schema name. We’ll need this to set up our pipeline

Pipeline Overview

The source code for our pipeline can be found. Copy the contents of this JSON to a new Graph within the Data Intelligence Modeler. If you’re not familiar with how to do this, you can refer to the README

When the pipeline starts, a GET request is made to the Ariba API. If there are more records to be fetched, the pipeline will make further requests until it has all available data. To avoid breaching Ariba’s rate limiting, there is a delay of 20 seconds between each call

Once all of the records have been fetched, the Document Store Collection is truncated to remove outdated results, and the most up to date data is inserted into our collection

1. A copy of the data is stored as a flat file in the DI Data Lake as reference
   
2. The HANA Document Store Collection is truncated, and Documents are added to the Collection one at a time
   
3. Once all records have been added to the Collection, the Graph will be terminated after a configurable buffer time (1 minute by default)

Configuring our Pipeline

In order to run this pipeline, you will have to make some changes to the pipeline:

In the Format API Request Javascript Operator, you should set your own values for openapi.header_params.apiKey and openapi.query_params.realm

If your Connection names are different to ARIBA_PROCUREMENT and ARIBA_HDI, then you will want to select those under Connection for the OpenAPI Client and SAP HANA Client respectively

Check the Path values for the operators “Write Payload Flat File” and “Write Error Log”. This will be where the pipeline will write the Flat File and API Error Logs respectively. If you’d like them to save elsewhere, edit that here

Finally, we’ll want to set the Document Collection Schema name in the DocStoreComposer Operator. This is the Schema we noted earlier while setting up the Connections

Testing our Pipeline

Now we’re ready to test our pipeline. Click on Save, then Run

Once our pipeline has completed successfully, we’ll be able to see that our JSON Documents are stored within our Collection by checking in the Database Explorer. We can access this easily through Business Application Studio by clicking the icon next to our SAP HANA Project

We can see that our pipeline has been successful, and that 206 JSON Documents have been stored in our Collection

Wrap-Up

In this blog post we’ve walked through how we can use SAP Data Intelligence Cloud to extract data from SAP Ariba, before storing it in a collection in SAP HANA Cloud’s Document Store

The post Ariba Analytics using SAP Analytics Cloud, Data Intelligence Cloud and HANA DocStore – Part 1 appeared first on ERP Q&A.

The purpose of this blog is to provide a detailed view of the Ariba SCC- Subcontracting end-to-end transaction flow along with screenshots of both Ariba and SAP ERP systems. This article will help the Ariba Consultants in visualizing the end-to-end transactional flow of Ariba SCC- Subcontracting.

Subcontract Manufacturing Collaboration is an outsourcing of certain production activities that were previously performed by the manufacturer to a third-party. Ariba SCC enables buyers and contract manufacturers to manage the supply of component materials and finished goods through Ariba Network.

Capabilities of Ariba SCC – Subcontracting:

• Informs Supplier about product ordered and components to be used
• Enables buyers to advise Supplier of component OH inventory and shipment
• Enables Supplier to report real-time receipt and consumption of components ensuring greater predictability of supply

Benefits of Ariba SCC – Subcontracting:

• Allows buyer to reduce production cost while maintaining visibility and control into contract manufacturing process
• Improves visibility into availability of supply, inventory, and production status
• Drives greater efficiencies between multiple supply chain parties

2. Ariba SCC- Subcontracting Process:

• Subcontracting PO:

Subcontracting PO with item category L is created in SAP ECC/S4 by the buyer. The Components tab in the PO will contain the components to be sent to the supplier for Finished goods manufacturing.

The price of the subcontracting material is determined from the Purchasing info record.

Based on the Purchasing info record setting either real time or back flush component consumption can be configured.

The PO output message is sent to the supplier on Ariba network:

• Subcontracting PO Confirmation:

The Supplier reviews the Subcontracting PO details on Ariba network and creates Order confirmation to acknowledge the PO.

The Order confirmation is sent to SAP ECC/S4 and can be viewed in the confirmations tab of the PO in ME23N transaction.

• Issue Component to the Subcontracting supplier:

Buyer creates outbound delivery for Subcontracting PO in SAP ECC/S4 using transaction ME2ON.

Buyer creates Post Goods issue using transaction VL02N and the component is issued to the supplier.

The Supplier can validate the outbound delivery in Ariba network using the path -> Extended collaboration->Component Shipments

• Component Acknowledgement in Ariba network by Supplier:

Supplier creates component acknowledgement in Ariba network once he receives the components from buyer.

The component acknowledgement created by supplier is sent to SAP ECC/S4 and updated as Proof of delivery. The Proof of delivery can be validated in SAP ECC/S4 using transaction VLPOD.

• Component Consumption by Supplier:

The Supplier creates component consumption in Ariba network for the components used in manufacturing finished goods.

The Component consumption creates a material document with movement type 543 in SAP ECC/S4

Ariba SCC supports both real time and back flushing for component consumption.

• If the Buyer opts to receive component consumption information in real-time, CM will have to complete a consumption report after components have been used.
• The report will update the Buyer’s ERP by consuming the component inventory against the Subcontracting PO
• If the Buyer opts for backflushing (component consumption at the time of finished goods receipt) instead, CM does not need to report consumption. The Buyer’s ERP will have to be set up to consume components upon receipt of the finished goods – either based on the BOM quantity or actual usage.

• Ship Notice by Supplier in Ariba network:

Once the finished goods are manufactured by the supplier and he is ready to ship them to the buyer, the supplier creates Ship notice (ASN) in Ariba network.

The ASN is sent as inbound delivery to SAP ECC/S4 and can be viewed in the confirmation tab in the PO

• Goods receipt in SAP ECC/S4:

The stores person creates goods receipt in SAP ECC/S4 upon receiving the finished goods using transaction MIGO.

The Goods receipt output message is sent to the supplier on Ariba network using output type WE03.

The supplier validates the goods receipt in Ariba network against the Po number:

3. Ariba SCC – SAP ECC/S4 Subcontracting Integration overview:

The flow of documents between Ariba SCC And SAP ECC/S4 during Subcontracting collaboration is shown below:

The post Ariba SCC – Subcontracting Collaboration appeared first on ERP Q&A.

Client is using Ariba Buying & Invoicing solution integrated with S4HANA ERP. Purchase Requisitions are being created in Ariba and once the Purchase Requisition (PR) is approved in Ariba, it sends the information to S4HANA to create the Purchase Order (PO).

If PO successfully created in S4HANA, Ariba receives the PO number back from S4HANA & PR/PO status changed to Ordered. If PO failed to get created in S4HANA, Ariba receives the error message details.

Currently, there is no real-time validation of the data captured on the Requisition before submission & sent for the approval. Ariba receives error messages only once the PR is fully approved and sent to S4HANA for PO creation. Client is looking for a solution where the PRs can be validated in S4HANA before the submission.

Ariba’s Real-Time Budget Check interface functionality (RTBC hereafter) is being proposed to not only validate the budget in ERP but also to check the requisitions validations in S4HANA. This will further reduces the errors which are being sent from S4HANA during the PO creation stage.

1.1 Applicable Module(s)

The solution covered in this blog will be applicable to the following Modules(s):

ERP- Backend System : SAP S4HANA On-premise

Middleware : SAP Cloud platform integration

2. Solution/Configuration Details

Solution offers to validate the Requisitions during submission is SAP Ariba’s standard feature Real-time budget check.

When user initiates a budget check voluntarily on a Requisition or during requisition submission by the system, Ariba triggers the synchronous call and sends the message to Cloud Integration Gateway. CIG will send this message post processing to CPI, where CPI will just be a pass through to send the Budget check request message to SAP ERP (S4HANA ERP). SAP ERP validates the request message and respond back with success or failure. S4HANA will creates a corresponding Purchase Requisition and return with SAP ERP Purchase Requisition reference number.

2.1 Solution Overview

Real-time budget check interface will trigger at below scenarios to validate the Ariba Purchase Requisition with budget maintain in SAP S4HANA and other Requisition validations.

2.2 Steps for Configuration

Real-time budget check functionality requires configuration in SAP Ariba, CIG, S4HANA and CPI.

Please follow the below sections for the details

2.2.1. Configuration in SAP Ariba

1. Below are the parameters to be enabled by raising the Service Request with customer support of SAP Ariba

2. Web-Services to be enabled in SAP Ariba @ Ariba > Core Administration > Integration Manager > Cloud Integration Gateway

• Export Requisitions for User-Initiated External Budget Chec
• Export Submitted Requisitions for External Budget Check
• Export Requisitions to External System to Revert Funds
• Export Modified Requisitions To Revert Funds
• Export Submitted Requisitions for Budget Checks Using SAP Ariba Cloud Integration Gateway

2.2.2 Configuration in CIG

Web-services used to integrate Requisitions as part of real-time budget check functionality are synchronous calls and there is separate iFlow in CPI to be configured. Due to this reason, a separate Project has to be created with individual connections for each of the synchronous services to be used for Real-time budget check integration.

Below are the two connection details to be maintained:

DocumentType: RequisitionBudgetCheckExportRequest/RequisitionExportRequest

Document Type : RequisitionRevertExportRequest

Note: Please repeat the same parameters for production connections.

CIG Project Details

Connections maintained above is being used in a project created specifically for synchronous services.

Note: RTBC services are synchronous webservice unlike other Ariba Buying & Invoicing asynchronous webservices. For mediated connectivity with CPI, separate project for RTBC synchronous webservices is required.

Please refer cloud integration gateway guide to know more about CIG project creations.

Project Name: Client_P2P_RTB

Cross-Reference – Parameters Maintained as below. We are using a separate doc type of SAP S4HANA for creation of requisitions from Ariba, which needs to be maintained as below in CIG.

Note: Please add the connections created for production RTBC webservices in this project only following the same above process.

CIG Custom Mapping

If required, custom mappings to be done at below mentioned cXML Document Type. As being the synchronous calls, payloads of this transaction are not visible in CIG and cannot be downloaded through transaction tracker in CIG.

2.2.3 Configuration in Middleware (CPI)

Deploy the standard I-flow as below in CPI instance

Package Name-

SAP ERP and SAP S/4HANA Integration with SAP Ariba Solutions

https://lxxxxxx-txx.hci.eu2.hana.ondemand.com/itspaces/shell/design

I-flow Name-

SOAP Synchronous Pass Through Content for Ariba Procurement

Validate the value mapping table bi-directional values.

2.2.4. Configuration in ERP

2.2.4.1. MM Configurations

Details of new doc type for Ariba PR – We have created new document type ZEX for Ariba Purchase Requisition.

Note: As being synchronous webservice, message payloads are currently not visible in CIG. For troubleshooting in your test environment, payload trace can be enabled in SAP S4HANA using srt_util t-code.

For any integration issues, please debug ARBCIG_PREQ & ARBCIG_PREQ_Delete FM.

2.2.4.2. SOAMANAGER Configurations

Please ensure the appropriate Web Service configuration in SOAMANAGER, as shown below.

BuyerPurchaseRequisition_Sync_

BuyerPurchaseRequisitionDelete_Sync_In

3. Benefits

• Real-time check of the budgets available in the back-end ERP
• Reservation of budget in ERP for the Requisitions created in SAP Ariba
• Validation check of the Ariba requisition data, resulting lesser failures at Purchase Order creation interface.
• Lower End to End cycle time by automating validations and budget check with backend ERP.
• Better user-experience by using budget check button.

The post SAP Ariba Real-Time Budget Check in Mediated Connectivity using CIG and CPI appeared first on ERP Q&A.

What Is SAP Ariba?

SAP Ariba is a cloud-based newer solution that permits suppliers and buyers to blend and do business on a single platform. SAP Ariba improves the overall vendor management system of an organization by offering less costly procurement methods and making business methods simple. Ariba works as a supply chain, procurement service to perform global business. SAP Ariba digitally transforms your procurement, supply chain,  and contract management process.

What Is the C_ARP2P_2008 Certification All About?

The C_ARP2P_2008, SAP Certified Application Associate – SAP Ariba Procurement certification exam validates that the candidate is versed with the basic knowledge in the area of the SAP Ariba Procurement solutions. The C_ARP2P_2008 certification also proves that the candidate has an overall understanding of the SAP Ariba Procurement application consultant’s profile and can use his knowledge practically in projects under an experienced consultant’s guidance.

What Type Certification Is the C_ARP2P_2008 Certification?

The C_ARP2P_2008 certification is recommended as an entry-level degree to allow consultants to get familiar with the SAP Ariba product line’s fundamentals. The C_ARP2P_2008 version of the exam takes part in the Stay Current with SAP Global Certification program. Once a candidate passes this version of the exam, he must start his stay current process with the subsequent quarter. A candidate needs to take the quarterly Stay Current evaluation for all subsequent SAP Ariba Procurement solution releases via the SAP Learning Hub. to keep his SAP Ariba Procurement business consultant certification badge and status. To take part in the Stay Current program and use the Stay Current enablement and assessment, A candidate needs a minimum an SAP Learning Hub, edition for Procurement, and Networks subscription.

Topics Covered under the C_ARP2P_2005 Syllabus:

A candidate must gain knowledge in the following areas-

• Basic Guided Buying Concepts
• Consulting
• Forms and Extensions
• Best Practices
• Integration
• Procurement Knowledge
• SAP Ariba Procurement Software Knowledge

How Should You Prepare for the C_ARP2P_2008 Exam?

Follow the Registration Method First:

Pearson Vue conducts the C_ARP2P_2008 exam. A candidate can register directly from Pearson Vue. Registering for the exam would make a candidate aware of the exam date and start preparing accordingly. The C_ARP2P_2008 exam 180 minutes long exam consisting of 80 questions. A candidate needs to get 69% marks to pass the exam.

Focus on the C_ARP2P_2008 Syllabus:

Passing an exam is always dependent on the completion of the syllabus. SAP Ariba is not easy, so a candidate should take enough time to prepare for the C_ARP2P_2008 exam syllabus. SAP syllabus is always percentage-based, so a candidate must plan well how much he wants to complete within how much time. Making short notes from important topics could be highly beneficial to revise the syllabus quickly.

Assess Yourself through Regular C_ARP2P_2008 Practice Test:

Where do you stand at your preparation? Knowing the answer is very important to improve further. A candidate can assess himself quickly through the C_ARP2P_2008 practice test. Practice tests point out the weakness and strengths of a candidate. Continuous hard on weaker syllabus sections could earn a candidate higher marks in the SAP Ariba Procurement exam.

Read Also: E_S4HCON2019 Exam: Use the Most of SAP S/4HANA through It

Some Features of SAP Ariba:

• SAP Ariba is a B2B solution that permits a user to connect to the world’s largest network of vendors and suppliers and grow business agreements with the right business partners.
• SAP Ariba allows businesses to connect with the right suppliers with deep visibility to your inside vendor and procurement management processes giving way to error-free business transactions.
• With SAP Ariba, a user can directly connect the Ariba network with millions of suppliers, meeting your business needs, and managing the supply chain.
• SAP Ariba network removes overall complexity in the procurement process, and suppliers and buyers can manage all key terms of vendor management on a single network.
• With the acquisition of SAP, Ariba can easily integrate with different SAP ERP solutions like SAP ECC and S/4 HANA with easy to configure workflows to automate different processes in the complete procurement cycle.
• You can easily integrate master and transactional data from different ERP solutions to Ariba processes.

Why Should You Become C_ARP2P_2008 Certified?

Better Growth Prospects with C_ARP2P_2008 Skills:

It is a popular fact in the IT world today that SAP C_ARP2P_2008, certified professionals, can opt for better job roles in the SAP domain. SAP domains are highly appreciated and demanded worldwide, so a certification with SAP Ariba could be a high confidence booster.

Better Salaries:

As SAP C_ARP2P_2008 certified, you can always gain an edge when it comes to pay scales. Many surveys proved that experts holding an SAP certification are generally paid higher for their skills and expertise, and the certification differentiate them from those who lack the certification. Though the salary may change based on the overall experience, educational background, and many other factors, holding the SAP certification undoubtedly acts as one of the key factors determining the pay packages.

The C_ARP2P_2008 Certification Earns Better Market Reputation:

Market surveys have revealed that SAP C_ARP2P_2008 certified individuals have better knowledge in the job market than non-certified peers. Being C_ARP2P_2008 certified means their knowledge and hence also earn higher preferences from employers.

Better Promotions Are Assured with C_ARP2P_2008 Certification:

When it is about your career, being SAP-certified can earn you a promotion. A certification is proof of your skills and guarantees your success.

Bottom Line:

The C_ARP2P_2008 certification is the pathway to earn knowledge in the SAP Ariba Procurement solution. SAP Ariba is a cloud-based Procurement solution that helps suppliers and buyers meet at one single network. SAP Ariba Partner program enables a candidate with tools, resources, and benefits to help build, run, and grow your business and career. So choose the right materials and get ready for your certification.

The post C_ARP2P_2008 Certification: Business Made Simple with SAP Ariba appeared first on ERP Q&A.