Skip to Content
Author's profile photo Former Member

Scheduling FI-CA related Delta Extraction

This document will guide through the steps involved in back ground scheduling of all FI-CA related delta extraction.

Introduction to FI-CA flow:

There are 3 main areas in FI-CA, Invoicing, Posting and Payment. Below is a small diagram illustrating the overall data flow of the SD & FI-CA, FI-CO.

Scheduling - 1.jpg

Explanation above illustration:

After SD billing has taken into place then the document created is Invoice. When Invoice is saved at the same time Posting document is also generated. Invoice is related to AR accounting where as Posting is related to GL Accounting.

Then afterwards when customer does the payment then Payment document is generated when payment is done via payment run or payment transaction (FPCJ, Cash journal, T-code).

BW Part:

As highlighted in red box in the above screen, I will go through extractors which are used for FI-CA data extraction.

Below are the extractors for each area:

  1. Invoice – 0FC_INVDOC_00 (FICA Extraction of Invoicing Document Data)
  2. Posting – 0FC_BP_ITEMS (FI-CA Business Partner Items) or 0FC_CI_01 (FICA Cleared Items for Interval) or 0FC_OP_01 (FI-CA Open Items at Key Date)
  3. Payment – 0FC_PAY (Payments)

Manual extraction of the FI-CA data into Delta Queue:

Below are the t-codes to extract delta/Init data into delta queue, manually.

Invoice –

  1. FKKINV_BW_MON (Analysis of BI Extraction Orders):: To monitor the records and simulation of Invoicing Extraction
  2. FKKINV_BW_MA (BI Extraction of Invoicing Documents):: To extract data into Delta queue

Posting –

  1. FPBW (BW Extraction of Open Items):: to extract Open BP Line Items
  2. FPCIBW (BW Extraction of Cleared Items):: to extract Cleared BP Line Items
  3. FPOP (Update of BP Delta Queue):: to extract BP Line items either Open or Cleared

Payment –

  1. FPCIBW (Update  Delta Queue):: to extract Payment Delta records (check the Payments tick box)

Delta Extraction:

Unfortunately all the above t-codes doesn’t have a functionality to schedule a background (batch) job to extract delta records, respectively.

1st Option::

In order to schedule the delta extractors we have an common t-code, FPSCHEDULER.

Before scheduling jobs in FPSCHEDULER we have to do 1 manual run to get the details for date of run and identification.

Scheduling - 2.jpg


  1. Select “Mass Activity Type”accordingly for each area as below;

BWOP – BP Line Items

2620 – Invoice

BWET – Payment

  1. Date ID & Identification – Need to pick up from old runs.

Scheduling - 3.jpg


In the Program menu, Execute in background.

Scheduling - 4.jpg

Select Output Device as LP01 or LOCL.

Scheduling - 5.jpg

After selecting the output device, select your schedule start time and Period values (frequency) accordingly. Accessing the below screen is as general scheduling screen.

Scheduling - 6.jpg


After saving the above schedule, you can check the Batch jobs in SM37. Job names will be created as below.

Scheduling - 7.jpg

2nd Option::

Another option in scheduler the jobs.

Go to SE38 (ABAP Program) t-code, give the program name as “RFKK_MA_SCHEDULER” then you can create as many variant as you can for respective areas.

Scheduling - 8.jpg


Scheduling - 9.jpg

Variant Values provided as:

Scheduling - 10.jpg

Based on the above 2 options we can do scheduling (batch job) for FI-CA related extractors.


Please provide your valuable feedback on the above guide.


Other documents from my knowledge base:


A step by step guide for Invoicing Extraction (FI-CA)

Triggering Process chain after completion of ECC Delta Extraction Job

Golden rules/Tips & Tricks for BW/BI Designing

Automation of the Data Load from SAP R/3 to BI

Design Solutions for BI/BOBJ Reporting (Part 1)

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Good document, flow is clearly explained.

      Author's profile photo Former Member
      Former Member

      It's really very good document and useful to every BW consultant  Ravi..

      Author's profile photo Former Member
      Former Member

      Excelent document Ravi, exactly what I was looking for! 🙂

      Author's profile photo Leslaw Piwowarski
      Leslaw Piwowarski


      I'm sure it'll be very usefull.

      Great idea !!!

      I think there should be created another documents like this (eg. FIGL FIAA).

      Author's profile photo Former Member
      Former Member

      Thanks one and all for your valuable feedback.

      @Leslaw Piwowarski - Sure. Let me pull some time to post those expected documents.

      Author's profile photo Former Member
      Former Member

      Good document Ravi....

      Author's profile photo Aparajit Banik
      Aparajit Banik

      Very Nice KT....
      Thanks for sharing....

      Author's profile photo Andrei Chirica
      Andrei Chirica


      I respect your steps, from both options, but I cannot schedule extraction from BWOP (0FC_BP_ITEMS extractor). I set values from step 1 and step 2, save it, but in sm37 transaction I don't see the programed jobs.

      Please can you help me?



      Author's profile photo Former Member
      Former Member

      Hi Andrei,

      Sorry for late response.

      Can you please check with Background user name for the programmed jobs in SM37?

      Thank you.



      Author's profile photo Jens Gehlenbeck
      Jens Gehlenbeck

      Hello Naga,

      is there a way to get mass simulation in FI-CA ... as a part of accrals ( german: Bilanzielle Abgrenzung ).

      The IS-U uses the data sources 0UC_SALES_STATS_0{1,2} for billing data and 0UC_SALES_SIMU01 for simulation which are both not applicable in FI-CA context.

      For billing we know - after reading your article - that we have to use 0FC_INVDOC_00.

      Whats about extraction of simulation in FI-CA context and the customizing of mass simulation ?

      Can you give any advice ?

      Thanks in advance,


      Author's profile photo Archana Ganti
      Archana Ganti

      Excellent. Thank you