|
Siebel Connector for SAP R/3 > Installation and Configuration > Siebel Configuration for Standard Integrations >
Changing Siebel LOV Definitions
Specific List of Values (LOV) definitions are predefined to support the setup of the required SAP Configuration data in the Siebel application. The SAP configurations in Table 12 must be defined within the List of Values (LOVs). Table 12 and Table 13 contain an SAP Reference column that you may use to find the applicable SAP configuration data in your implementation. Table 13 contains definitions that are provided as part of your Siebel installation.
Table 12. List of Values for Customizable SAP Configuration Data
|
|
|
Language Independent Value |
|
Blocking Reason for Billing |
SAP_SO_
HEADER_
BILL_BLOCK |
SAP Description
example: Calculation Missing |
SAP Code
example: 01 |
SAP transaction ovv3
IMG section: Sales and Distribution > Billing > Billing Documents > Define Blocking Reason for Billing, select Billing: Blocking Reasons |
Customer Account Group |
ACCOUNT_
GROUP_TYPE |
SAP Description
example: Sold to Party |
SAP Code
example: 0001 |
SAP transaction OBD2
IMG Section: Financial Accounting > Accounts Receivable and Accounts Payable > Customer Accounts > Master Records > Preparations for Creating Customer Master Records > Define Account Groups with Screen Layout (Customers) |
Delivery Blocks |
SAP_SO_
HEADER_
DELIV_BLOCK |
SAP Description
example: Credit Limit |
SAP Code
example: 01 |
SAP transaction ovlx
IMG section: Logistics Execution > Shipping > Deliveries > Define Reasons for Blocking in Shipping, select Delivery Blocks |
Sales Organization |
SAP_SALES_
ORG |
SAP Description
example: Europe |
SAP Code
example: 0010 |
SAP transaction OVX3
IMG section: Enterprise Structure> Assignment > Sales and Distribution > Assign Sales Organization to Company Code |
Distribution Channel |
SAP_
DISTRIBUTION_CHANNEL |
SAP Description
example: Retail |
SAP Code
example: 10 |
SAP transaction OVXK
IMG Section: Enterprise Structure > Assignment > Sales and Distribution > Assign Distribution Channel to Sales Organization |
Division |
SAP_DIVN_CD |
SAP Description
example: Software |
SAP Code
example: 10 |
SAP transaction OVXA
IMG Section: Enterprise Structure > Assignment > Sales and Distribution > Assign Division to Sales Organization |
Plant |
SAP_PLANT |
SAP Code
example: 10 |
SAP Code
example: 10 |
SAP transaction OVX6
IMG Section: Enterprise Structure > Assignment > Sales and Distribution > Assign Sales Organization - Distribution Channel-Plant |
Table 13. List of Values for Seeded SAP Configuration Data
|
|
|
Header Delivery Status |
SAP_SO_HEADER_DELIV_STATUS |
SAP Transaction SE11
Valid values for Domain STATV (Document status) |
Item Delivery Status |
SAP_SO_ITEM_DELIV_STATUS |
Same as Header Delivery Status |
Overall Status |
SAP_SO_OVERALL_STATUS |
Same as Header Delivery Status |
These definitions must be made consistent with your SAP configuration data. Compare these definitions with the values in SAP and make changes as required. Table 13 contains an SAP Reference column that you may use to find the correct SAP configuration data in your implementation. This column contains an SAP transaction code in which you can view the configuration data as well as a reference section to the SAP Implementation Guide (IMG) where applicable. This information is correct for SAP R/3 4.6C. It may vary in other SAP versions. To make sure the required SAP entities are copied into the Siebel database, you should synchronize the LOV types. To synchronize LOV types
- In the Siebel client, navigate to Administration - Data and select List of Values.
The following figure shows the List of Values list with its Type, Display Value, Language Independent Code, Language Name, Parent LIC, Order, Active, Translate, Multilingual and Replication Level fields.
- Query for each LOV Type in the List of Values list to see predefined values.
- Navigate to the SAP Reference area using an SAPGui client application to see the values defined in SAP.
- If differences exist between the definitions in the Siebel repository and SAP, correct or add entries in the Siebel repository as necessary.
- Repeat Step 2 through Step 4 for each LOV type.
|
