0FI_AR_4

Accounts Recievable : Line Items - Customers: Items

Tables
BSAD ( Cleared Items )
BSID ( Open Items )


Delta Pointer Table
BWOM2_TIMEST

Related T-codes :
FBL5N : This gives the data for Customer Line Item

Source Fields Link from SAP
https://help.sap.com/saphelp_nw70/helpdata/en/2f/ea8953d7363d58e10000000a174cb4/frameset.htm

0FI_AA_12

FI-AA: Posted Depreciations

It is part of Asset Accounting.
This DataSource supplies the values of depreciation postings by period. Depreciation values are simulated for periods that were not yet posted.

Base Tables
ANLP

TCode
AS03
AW01N

Delta DataTable
BWFIAA_AEDAT_TR

Delta Pointer Table
BWOM2_TIMEST
Delta for this extractor is dependent on the successful delta triggers for 0ASSET_ATTR_TEXT and 0ASSET_AFAB_ATTR. If the deltas do not get any records/pointers not updated in delta pointer table, there will be no delta records for this datasource and also, 0fi_aa_11 datasource.



Help.SAP.com : Link

ASSET extraction

SIM / FIAA_SIM field
It is the simulated field.The type of simulation depends on the following parameter maintained in the system.

Table : BWOM_SETTINGS
Param_Name : BWFIAASIM

This datasource gives the asset depreciations till current month along with simulations for the rest of the year.The simulation values get calculated on run time.

SIM = 'X' - Simulated values.
SIM = <blank> -  Real Values
SIM = 'N'. - real values -> no carryforward

When the datasource is run FULL - We get 'BLANK' values for existing values and 'X' for simulated ones.

When run DELTA, - we get  'BLANK' and 'N' values for existing and new records and 'X' for simulated. Right now, not sure on what exact difference is between the <blank> and N values, however, in the standard BI content flow given for this extractor which goes to DSO 0FIA_DS13, the N values are filtered out in the start routine.

Internal Function Modules
BWFIAA_GET_DEPR_DELTA

InfoCubes

Activating Infocubes
When data is already present in the infocube and a new field is added, data in the infocube has to be dropped and loaded ( as the cube has to adjust the dimension tables data according to the new changes). if not done , DTP would fail.

also check activation
Try RSD1 and press infocube option at the top then proceed with utilities of infocube and go for activation of infocube. A program will appear try to run that program in background which will help you in getting the infocube activation.

Or Try running the program RSDB_CUBE_ACTIVATE in background. Foreground sometimes go for time out hence it is difficult to activate in foreground.

If some error persists try using RSRV and correct the cube inconsistencies then proceed with activation of cube.

Flat Files

Points to Remember
- When loading data from a flat file, the datasource will take the default lenghts from the file. If a particular field is not populated in the flat file, it might take 1 as length , which will cause

Error
Overflow converting from on assignment field
Error 'Overflow converting from '12345'' on assignment field zfield record 9 value 12345

Reason : The type of the flat file and BW are different. change type / increase the length of the fields.
Eg : the field length is 6, but in your datasource it is type INT2 which is max of 5. Change it to INT10 or CHAR

12 Shipping / Deliveries - COPIED

Base Tables
LIKP - SD Document: Delivery Header Data
LIPS - SD document: Delivery: Item data


T-Code
VL01/02/03 ( outdated )

Outbound Deliveries : VL03N
Inbound Deliveries    : VL33N

SetUp Tables
Delete Setup tables : LBWG (12)
Filling Setup           : OLI8BW - RMCVNEUL

Enter some values in selection screen - else, the job will error. eg: give comp code from 0001 to 9999

Setup tables can be run based on ERDAT ( Created On ) / AEDAT  ( Changed At ) from LIKP and LIPS  for selective full load of data ( for failed delta / V3 jobs ).
Follow the procedure HERE to run setup tables for multiple single values.

2LIS_12_VCHDR

This datasource gets the header details of all delivery documents.

Helpful Links : SAPHelpNotes

2LIS_12_VCITM

This datasource extracts all item level data for OUTBOUND deliveries.

Inbound deliveries are not extracted with this datasource.

Inbound deliveries are MM deliveries. Vendor to Purchasing organsiation .Inbound Deliveries comes into picture of Purchasing.So for inbound deliveries you have to seek MM extractors.Pls try extractors of procurement 2lis_02_scl, 2lis_02_sgr, 2lis_02_cgr.

Inbound delivery is the delivery document through which the goods reach the plant (in MM perspective,after purhcase order, we receive goods through tcode MIGO which is ntohign but inbound delivery)

Inbound delivery types adn the functionality are configured as a part of procurement process and hence in MM

Outbound delivery is the delivery document in sales through which the goods are issued to the ship to party.

Helpful Links : SDN Discussion1 ;  SAPHelpNotes

2LIS_12_VCSCL

Outbound Deliveries and Inbound Deliveries

Outbound Deliveries VL03N

If you want to send the material to customer Outbound delivery is required . 

The flow is in Sales process.

 Sales order --> delivery >Shipment>Billing against delivery.

You use this process in order to support all shipping activities like picking,packing,transport and goods issue.
All information regarding shipping planning is stored in outbound delivery,the status of shipping activities is monitored, and data gathered during the course of shipping processing is recorded.By creating outbound delivery,shipping activities are started and data is transfered that is generated during shipping processing

LIKP - VBTYP = 'J' or 'T'

Inbound Delivery  VL33N

Inbound delivery is required to receipt the material against PO from vendor.

You specify some dates in your PO for delivering material. 

However the vendor after seeing the PO, delays the delivery by own week because of lack of resource. He intimates you thru phone. So you create an inbound delivery with respect to the PO released on that vendor stating that the delivery will be exactly on so and so date.

This makes you to have the exact delivery schedule or otherwise it is a pre-intimation of vendor by when he could supply the material. Since this could be created automatically thru IDOC once vendor sends the information, This reduces processing time and data entry time when you receive the goods actually.

Inbound delivery does not necessarily mean goods receipt. INBOUND DELIVERY in SAP pertains to all incoming goods, which may refer to either a vendor delivery or a return of a rejected delivery to a customer. It may cover the schedules of deliveries from your vendors/suppliers or even a rejected delivery to a customer.

LIKP - VBTYP = '7'