Change Reference Characteristics of InfoObjects

Sometimes,
We create infoobjects referencing other infoobjects, but down the line, we might want to remove the reference  or change the reference or in some cases, add a new reference for the infoobjects.

SAP has provided a note for the same SAP NOTE 568051

https://launchpad.support.sap.com/#/notes/568051

Below are the steps as explained in the note.


Scenario 1
Replace the reference characteristic from one to another
In this scenarion,  we have an Infoobject ZCHILD which was created as a reference to ZMAIN1.

Now we wanted to replace the reference from ZMAIN1 to ZMAIN2.

Step 1 : Check the entry in table RSDCHA

Here change the value of 'M' entry to the reference character wanted.Here to ZPMAIN2 either directly in the table (most cases possible in dev systems ) or through program ( where edit not available)

Now go to table RSDIOBJ and make 'ACTIVFL' BLANK from 'X' for both 'A' and 'M' versions.

These changes will de-activate the infoobject.
Go to RSA1 and activate it. you can see that the reference object has been changed.

The activation would NOT happen if the Infoobject is being used in any infocubes with data in them. Delete the data from the infocubes and activate the infoobject.

Now, if you check the table, RSDIOBJ, the ACTIVFl would be changed back to 'X'.



Scenario 2

Version Management

Version management in SAP helps us to compare versions of objects within the system and also with other system.


Program --> Utilities --> Version Management

If a program is changed, and you wanted to see the new changes, version comparision can be done with the edited version Vs last active version available.

remote comparision
A program/object in development can also be compared with quality or production using version management.

Click on Remote comparsion and it gives a pop up for mentioning the target system you wanted to compare against. 

It gives you a list of all version available and click on ONE version you wanted to compare against and click remote comparison again. It shows you all difference.

Use 'Single-Column/Parallel' to adjust your view.

Sales

Setup Table Tcode     : OLI7BW
Setup Table Program / Job Name: RMCVNEUA
No selection criteria necessary for running the setup tables.
V3 Job Name :  RMBWV311

TCodes 
Sales Order : VA01 / 02 / 03
Sales Contract : VA43

Corresponding Tables

VBAK	Sales Header
VBUK	Sales Header Status
VBAP	Sales Item
VBUP	Sales Item Status
VEDA	Sales Contract Data

Points to Remember

Customer Purchase Order Number
VBAK-BSTNK and VBKD-BSTKD
This is for Customer PO. In VA03, if you do a F1 help on Customer PO, it will point to VBKD-BSTKD.
Then what is VBAK-BSTNK?
From my understanding , both are one and the same. VBKD field is CHAR 35 and VBAK field is CHAR 20. It is fine whatever field you pick from , but need to check the field value. If it more than 20, you might find truncated value in VBAK-BSTNK.

Refer 'SAP Forum Notes' for more information.

Contract Start and End Dates - VEDA
Contract start and end dates can be present at both header and item level.
If there is no item level dates maintained, header level dates flow to item level too.

Sales Inquiry Documents
Documents with Sales document category = A ( Inquiry ) will not be pulled by standard extraction. These documents can be seen in Sales document tables but the LIS extractors do not pull them.

Deleted LBWQ entries
Rarely, there may be a situation wherein a transport moved with out clearing the LBWQ entries with structure , which would fail the V3 Job.
In this scenario, we need to delete the entries in LBWQ for that queue. For sales, we do not know the criteria to do the full load. One way to get around this is to get the changes from CDHDR/CDPOS .

You can use program 'CHANGEDOCU_READ'.
For Sales : Give Object Class : VERKBELEG and run for date range. This should give you all the delta records which you might have deleted from the queue. ( ?? Not sure if this completely gets all the delta records, make sure you do a full load when time permits )

Sales Document Header

2LIS_11_VAHDR

Base Tables : VBAK , VBUK

Sales Document Item

2LIS_11_VAITM

Base Tables : VBAK, VBAP, VBKD, VBUK, VBUP

       

Sales Document Conditions

2LIS_11_VAKON

Base Tables : KOMV, VBAK, VBAP,VBKD, VBUK, VBUP

Notes
Pulls only ACTIVE conditions and Conditions with value(*) to BW.
KNOV-KINAK != 'Y'
Discussion  Links : Thread 390900

Sales Document Schedule Line

2LIS_11_VASCL

Base Tables : VBAK, VBAP, VBEP, VBKD, VBUK, VBUP

SAP Documentation : Here

Sales Document  Header Status

2LIS_11_VASTH

Base Tables : VBUK

Sales Document Item Status

2LIS_11_VASTI

Base Tables : VBUP

Sales-Shipping Allocation Item Data

2LIS_11_V_ITM

Base Tables : VBAK, VBAP, VBKD, VBUK, VBUP

Sales-Shipping Allocation Schedule Line

 2LIS_11_V_SCL

Base Tables : VBAK, VBAP, VBEP, VBKD,VBUK, VBUP

Sales Document Order Delivery

2LIS_11_V_SSL

No Maintenance structure is provided for this datasource
SAP Documentation : LINK

This data source does not bring in third party items. 
2lis_11_v_ssl is datasource of order delivery. Check if in table VBEP, for the sales document in question, field LFREL is marked with  "x" or not.  If the field is empty, it means that the sales order is not marked as delivery relevant, meaning that Datasource 2LIS_11_V_SSL won't extract the document

SAP Note : 729962
 2LIS_11_V_SSL: Third-party items are not extracted

SAP ECC functional tables

Customer Material Information(CMIR):

KNMTK - Customer Material Information: Header

KNMT - Customer Material Information: Item

Bill of Materials (BOM):

MAST - Material

EQST - Equipment

KDST u2013 Sales Order

DOST - Document

STST - Standard Object

TPST u2013 Functional location

STKO u2013 BOM: Header

STZU u2013 STL data

STAS u2013 BOM: Item selection

STOP u2013 BOM: Item data

STPU u2013 BOM: Sub items

Sales Activities & Sales Document (Header):

VBUK u2013 Header Status / Admin data

VBUV u2013 Incompletion log

VBPA u2013 Partner functions

SADR - Address

VBFA u2013 Document flow

VBAK u2013 Sales document: header

VBKD u2013 Sales document: Business data

VAKPA u2013 Partner index

VEDA - Contract

VBKA u2013 Sales Activity document

NAST u2013 Output

JSTO u2013 PP Status

STXH u2013 Text: header

STXL u2013 Text: Lines

Sales document (Item):

VBUP u2013 Item status

VBAP - Sales document: Item data

VBKD - Sales document: Business data

VEBA - Contract

VBLB u2013 Forecast

VBEP - Sales document: Schedule line

VBBE u2013 Individual requirement

VBBS u2013 Summary requirements

VBUV u2013 Incompletion log

VBFA u2013 Document flow

VBPA u2013 Partner functions

JSTO u2013 PP Status

NAST u2013 Output

STXH u2013 Text: Header

STXL u2013 Text: Lines

KONV u2013 Conditions

General:

AGR_USERS - Assignment of roles to users

CDHDR & CDPOS - Change history of master data and documents

TSTC - SAP Transaction Codes, maintained via transaction sm01

NAST - Message status

Shipping:

LIKP - delivery header

LIPS - Delivery item

LINK - inventory document header (WM)

LINP - inventory document item (WM)

VTTK - shipment header

VTTP - shipment item

VTTS - Stage of shipment

VTFA - shipment document flow

VTPA - shipping partner

LTAK - transfer order header

LTAP - transfer order item

VEKP - handling unit header

VEPO - handling unit item

Billing Document:

  VBRK   Billing Document Header

  VBRP   Billing Document Item

Info Record

Inforecords can be of different types.

Customer InfoRecords

Sometimes, customer refers to a material with their version of the name, rather than using the technical name in purchase order . So we need to map customer material name to company's material code and is process is done using Customer Material InfoRecord.

Uniquely identifies the material from the customer's point of view.

TCodes : Customer related
VD51 / 52 / 53

Tables : Customer related
KNMTK - Customer-Material Info Record Header Table
KNMT    - Customer-Material Info Record Data Table

Purchasing InfoRecords

Tcodes:
ME01/02/03 : Material Plant Level

Tables: 
EINA - Purchasing Info Record: General Data
EINE - Purchasing Info Record: Purchasing Organization Data