Session on SAPI

download Session on SAPI

of 16

Transcript of Session on SAPI

  • 8/12/2019 Session on SAPI

    1/16

    SAPI Overview

    Sai Kiran SPrepared on 26 April 2013

  • 8/12/2019 Session on SAPI

    2/16

    SAPI SAP Interface Interface between SAP and a variety of external

    (Bolt-on) systems for master & transactionaldata

  • 8/12/2019 Session on SAPI

    3/16

    Master data: Customer (CUST) Material (MATL) Passwords (WLPW) Access Categories (WLAC)

  • 8/12/2019 Session on SAPI

    4/16

    Transactional data: Order/Subscription (MYR, Deal, CMB,

    Promotion, MLA data) (ORDR) Invoice (INVC) Deferred Revenue (DREV) Service notes (SERV)

  • 8/12/2019 Session on SAPI

    5/16

  • 8/12/2019 Session on SAPI

    6/16

    SAPI-Consuming Systems:

    Commissions (ORDR, INVC) QuickView+ (CUST, MATL, ORDR, WLPW, WLAC?) Tagged for Deletion: WLQV 7/2011

    RAP (INVC, DREV) Royalties (INVC, DREV) WIBS (CUST, others?)

    Mastermind/MDB/CRM (SERV, WLPR) Data Warehouse (SERV)

  • 8/12/2019 Session on SAPI

    7/16

    Basic Architecture:

    Series of scheduled ABAP batch jobs: Stage 1: Create IDoc/data gathering Stage 2: Put IDoc/data segments into a staging

    table (still in SAP) Stage 3: Load a batch of segments into the

    external SAPI database

  • 8/12/2019 Session on SAPI

    8/16

    SAPI Database Schema Batch table (one record per to system per batch)

    System from/to Data class (ORDR, CUST, etc.) Processing status, dates Total counts

    Transaction table Batch ID, Source System Transaction serial, sequence #s Data class, type Transaction data (structured data payload field)

  • 8/12/2019 Session on SAPI

    9/16

    SAPI Programs Stage 2 Program :- SE38 - ZCAXXIO001_STAGING_OUT_TABLE

    This program retrieves the concerned IDOC data(customer / Order ) and fills the correspondingstaging tables:-ZTCA_STG_CUS_OUTZTCA_STG_INV_OUTZTCA_STG_MAT_OUTZTCA_STG_ORD_OUT

  • 8/12/2019 Session on SAPI

    10/16

    SAPI Programs Stage 3 Program :- SE38 - ZCAXXID002STAGING_OUT_DB2

    This program retrieves the data from the staging

    tables and sends them to concerned Bolt-Onsystems.

    If Successfully sent, it updates the log table

    ZTSD_SAPI_LOG and TVARV table with name'Z_OB_LAST_EXTRACT_DATE .

  • 8/12/2019 Session on SAPI

    11/16

  • 8/12/2019 Session on SAPI

    12/16

    Stage 1 Job ZRBDMIDOC (a job OCAT1205SAPICUSTS1 is run forevery 30 minutes). I manually run it for time being.

  • 8/12/2019 Session on SAPI

    13/16

    After the Stage 2 job/ program is run, the staging table isupdated with the partner changes:-

  • 8/12/2019 Session on SAPI

    14/16

    After the Stage 2 job/ program is run, Stage 3 Job is run(Daily once) to send the captured staging table data tothe Bolt on systems.

    To know the Job Names (as may get changed), go to thetable V_OP and give the program names (stage2 andstage3 programs) for a particular day.

  • 8/12/2019 Session on SAPI

    15/16

  • 8/12/2019 Session on SAPI

    16/16

    Questions?