Compounding

compounding attribute are nothing jst a combinaiton of two char to make a unique one i mean none of them is existant without the other or in other words there is no meaning if the are separated

Typically in a organization the employee id are allocated in serial like say 10001, 10002 and so on. Lets your Organization comes out with a new employee id scheme where the employee id for each location would start with 101. So the employee id starting for india would be india/101 and for US would be US/101. Now note that the employee india/101 and US/101 are different. Now if someone has to contact employee 101 he needs to know the location without which he cannot uniquely identify the employee. Hence in this case location is the compunding attribute.

A maximum of 13 characteristics can be compounded for an InfoObject. the characteristic values can also have a maximum of 60 characters. This includes the concatenated value, meaning the total length of the characteristic in compounding plus the length of the characteristic itself.

Data Loading

Lo related datasources.

• New Datasource
• Checking : Check the existing setup table to see if data is present in the setup tables. Go to SE16 and give the setup table name
• MC<Application Number>M_0<datasource>SETUP
• MC02M_0ITMSETUP
• Deleting : If data is present in the setup tables, delete them and re-load them again. Remember  that set up tables are filled for the whole application and not for each datasource.
• Set up table data will be deleted for whole 'Purchasing' if deleting for '02' even though you want data reload for only Purchasing Item datasource 2lis_02_itm.
• T-Code : LBWG 
• Or SBIW -> Settings for Application-Specific Datasources(PI) -> Logistics  -> Managing Extract Structures -> Initialization -> Delete the contents of the setup tables  
• Filling : Go to corresponding t-code for each application (unlike deleting, filling setup table t-code is different for each application or Goto SBIW ->  SBIW -> Settings for Application-Specific Datasources(PI) -> Logistics  -> Managing Extract Structures -> Initialization -> Filling in setup tables -> Application Specific setup of statistical data -> (choose your application)
• Depending on the screen you get over there, selections can be given and data can be filled to the setup tables or you can run it wide open.
• Remember to run in background, so that its easy to monitor and know the status. The job will be scheduled under job name 'RMCENEUA'.
• Once the job is completed, the data is available to load to BW Via 'Full Update'
• Existing datasource
• Once the new field is added to the datasource, there are two ways to go.
• Historic data is not required for the new field
• So we need not do anything. Just add the field and the code if needed any in the exit and  let the regular process chains get the delta and fill the data
• Historic data needed
• For this we need to do a full load. So we need to follow all the steps as for a new datasource and fill the history.
• Looks for downtime ( when the delta's are not running) Fill the setup tables and do a full load to BW and to the infoprovider. It will take care of the existing data and also writing data to the new fields.
• Delta need/will NOT be disturbed. No Initialization is required. 

BI Content

Steps to follow while installing BI content
-----------------------------------------------------
Select the objects which are needed and drag them to the right side.

In grouping , make sure you are doing only necessary objects.

If upwards and downwards data flow is needed  (transformations and dtps etc), identify the object from the list , go back and search for the object in the left side - drag it individually and install it.

Go for Tree View instead of Hierarchy View ( which is the default view ) , to see a better view of the objects.

Remember, clicking on the parent, will select all the objects below it, even though they are not selected. you need to take care and select individual objects to install them.

Right click and select 'Donot Install any below' to make sure.

Better option would be to get the technical names of the individual transformations or dtps, whaterver needed from the flow and then install each object individually searching for them in the contect. This way, you are installing only necessary objects.

Datasources

Replication :
Goto RSDS -> Datasource and Source System -> Replicate

Purchasing

Purchasing

Link for information in help.sap.com
Information from SAP content

Datasources

Setup Table Structure                : MC02M_0(HDR)SETUP
Deleting Setup tables                 :  LBWG - Application : 02
Setup Table deletion job name   :  RMCSBWSETUPDELETE
Setup Table Filling Job Name      :  RMCENEUA
Filling setup tables                     : OLI3BW

Points to Remember

• Purchasing Extractors  do not bring records which are incomplete. i.e. EKKO-MEMORY = 'X' - Incomplete.
• PO Item marked for deletion in ECC but the same is not reflecting in BW via delta/full loads. Click HERE

Tables
EKKO
EKPO
EKBE
EKKN


Transactions
ME23n
ME2L ( Account Assignment )

2LIS_02_ITM

SYDAT is Item created on - EKPO-AEDAT.
In LBWE, it says EKKO-SYDAT but it is from EKPO (*)

2LIS_02_ACC

Base Tables 

EKKO - Header

EKPO - Item

EKKN - Account Assignment in Purchasing Document

2LIS_02_ACC- NETWR

Even though the extract structure shows EKKN as the base table for this field, it is actually  calculated using a formula ( Check SAP notes Link for more )

For documents with specified purchase order quantity, such as purchase order documents, the net purchase order value is calculated as follows:

NETWR = EKPO-NETWR / EKPO-MENGE * EKKN-MENGENet purchase order value = Net purchase order value of item / Item quantity * Quantity posted to account

For documents with target purchase order quantity, such as contracts, the net purchase order value is calculated as follows:

NETWR = EKPO-ZWERT / EKPO-KTMNG * EKKN-MENGENet purchase order value = Target value of item / Target quantity of item * Quantity posted to account

2LIS_02_ACC-LOEKZ
In the extractor structure value of LOEKZ is from EKPO but there is no data coming from the extractor. LOEKZ is passed to ROCANCEL internally and if ROCANCEL is mapped in the DSO, those items are deleted as LOEKZ is deletion indicator. If you need LOEKZ value, fetch it in the enhancement in a zfield.



SAP Notes Link
https://help.sap.com/saphelp_nw70/helpdata/en/f3/487053bbe77c1ee10000000a174cb4/frameset.htm