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-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 )
Base Tables : VBAK , VBUK
Base Tables : VBAK, VBAP, VBKD, VBUK, VBUP
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
Base Tables : VBAK, VBAP, VBEP, VBKD, VBUK, VBUP
SAP Documentation : Here
Base Tables : VBUK
Base Tables : VBUP
Base Tables : VBAK, VBAP, VBKD, VBUK, VBUP
Base Tables : VBAK, VBAP, VBEP, VBKD,VBUK, VBUP
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
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 NumberVBAK-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
Sales Document Item
2LIS_11_VAITM
Sales Document Conditions
2LIS_11_VAKONNotes
Pulls only ACTIVE conditions and Conditions with value(*) to BW.
KNOV-KINAK != 'Y'
Discussion Links : Thread 390900
Sales Document Schedule Line
2LIS_11_VASCLSAP Documentation : Here
Sales Document Header Status
2LIS_11_VASTH
Sales Document Item Status
2LIS_11_VASTI
Sales-Shipping Allocation Item Data
2LIS_11_V_ITM
Sales-Shipping Allocation Schedule Line
2LIS_11_V_SCL
Sales Document Order Delivery
2LIS_11_V_SSLSAP 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
No comments:
Post a Comment