SIS Tables

Hi
We have a self defined Info structure which had characterstic-Line of business it says Ref Table MCVBRK and source table is MCVBRK ref field ZZLOB.source field ZZLOB.
My question here is, for a specific invoice if i wanted to check entries in MCVBRK system says there is no table.. i feel its a structure, then how can a check whats this field is and from its getting updated, in the info structure.
When i run MCVV for this invoice its updating in diff info structures i wanted to know what are all the fields from the invoices are getting updated into there strcutures?
Reg
Shankar124

MCVRBK is a structure, one can view the details for the same using the trasaction se11. The table attached would be VBRK-Billing Document: Header Data.
Go to
IMG>Logistics General>Logistics Information System (LIS) for checking the complete set-up as to how the SIS structures are defined and used.
For checking the structure being updated in transaction MCVV, check the transaction-MC21.
Path: IMG>Logistics General>Logistics Information System (LIS)-Logistics Data Warehouse>Data Basis>Information Structures>Maintain self-defined information structures.
Check the following link for complete details about LIS set-up
<a href="http://www.sapfinancialsexpert.com/downloads/11-02.doc">LIS Set-up</a>
Regards,
Gaurav
Reward Points if the solution is helpful.

Similar Messages

Fields in SIS tables

Hi,
How are the fields in SIS tables (like S800, S601 etc..) being poultaed. Where are these fields coming from...

Hi...
The fields in SIS tables are populated automatically when sales order/Shipping / Invoice Documents are created in transactions VA01/02, VL01/02 and . For details of updation rules please check transaction code MC26.
Please confirm if this answers your question.
Regards,
MS

Archiving 40% of ECC DB u2013 (SIS tables) u2013 functionality moved to BI

We are going to archive/delete approximately 50% or 1.6TB of SIS data from our production ECC database.
We are new to running SAP on SQL Server 2005 and need to know if there are any tasks like reorgs that should go along with removing this amount of data from the DB. I am concerned that performance can be affected. I understand that during the removal of the data we need to watch our Tlogs.
The data will be removed from SIS tables and most of them will be completely cleared but some of them may still be in use.
Any input would be greatly appreciated.
Regards,
Diane Szmurlo

Be careful when Archiving and Don't delete the archive files. Some transactions still look for entries in the archived data.
At one clients site there was a serious performance problem after archiving some data. Some config was changed on some FI transactions that looked for field entries that were not there before the archiving. Needless to say, they had to trace the problem down and rewrite the config.
Always Test, Test, Test before going to production.

Incorrect update SIS table for Product Allocation

I have set up product allocation, use a custome table S501.
S501 contains characteristics fields:
KONOB: Product allocation object
VKORG: Sales Org.
VTWEG: Distribution Channel
ZZREGION: Region (custom field)
MATNR: Material code
When I create and save a sales order,
VKORG and VTWEG are updated as "***" and "*" in table S504.
ZZREGION and MATNR are updated correctly.
Could you please kindly advise how sales org. and dist. chan. can be copied to table S504 correctly? Thanks.

If the challan has 2 or more line items & one of the line item is fully reconciled thats why it is showing the status F in item detail table & P in header table of challan

Tables for Credit data

Hi all,
please tell me the tables for Credit data.
Thanks,
kishore.

1) Check to see if there are any entries in table S066 and S067. These SIS tables hold the credit data for sales order value and delivery order value.
hope it helps

InfoPackage definition for Bespoke SIS Structure

All
I have a bespoke SIS R/3 Structure which I need to extract data from and import into BW. Everything is setup, but I am having trouble with defining my InfoPackage.
In the SIS structure there is a field called Version (VRSIO), which has a default value of 000. This is the value that Actual Sales are recorded under.
There are other Versions in the SIS Table which relate to Sales Forecasts and Sales Budgets etc. So, my InfoPackage specifically has to extract the 000 records.
If I define my InfoPackage to manually select VRSIO=000 I get a failed load and no data selected from Source System and an error in BW Monitor stating
The actual data cannot be selected using version '000'! M+ 47
I then tried to use an ABAP routine to define VRSIO (I am not an ABAP developer though!) but got the same error.
 read table l_t_range with key
 fieldname = 'VRSIO'.
 l_idx = sy-tabix.
 l_t_range-SIGN = 'I'.
 l_t_range-OPTION = 'EQ'.
 l_t_range-LOW = '000'.
 modify l_t_range index l_idx.
 p_subrc = 0.
Amended the following and got a new error message
For sel. field 'VRSIO ', no selection with SIGN = 'I '; OPTION 'LT ' allowed RSM1 607 
 l_t_range-OPTION = 'LT'.
 l_t_range-LOW = '001'.
Amended the following and got no error message but retrieved no data
 l_t_range-OPTION = 'EQ'.
 l_t_range-LOW = ' '.
Amended the following and got no error message but retrieved no data
 l_t_range-OPTION = 'EQ'.
 l_t_range-LOW = ''.
Has anybody got any ideas which might help me? PLEASE!!!????!!!???

Hi Simon,
I suppose you have a Sxxx InfoStructure connected to your BW. Did you do this by creating the DataSource in Trans. LBW0 ?
Then you will have an additional field, which is not in the normal InfoStructure, named "value type" (WRTYP). The acutals (Version = '000') get a WRTYP = '010' (actual).
The other versions get different value types. This is done in the extractor. You can select in your InfoPackage on WRTYP = '010'. Then you should have everything in Version = '000'.
Hope this helps.
BTW, when you want to extract sales orders, you sould switch to the LBWE logisics extractors.
Regards,
Frank

Any particular risks when archiving SIC tables ?

Hi,
I'm about to launch archiving sessions for SIC tables : S001, S003, S006 ans S033. These tables are growing fast indeed in our system and nobody in my company uses SIC transactions.
Is there a risk to archive these tables, eg. if I archive them after just one month of residence ?
Could the SD SAP BI extractors be impacted ?

Hi Serge,
... as Sales orders are created in a legacy system and then copied to SAP using IDOCs in order to be invoiced and then posted into accounting (FI)
Yeah, that's quite usual for the first step of a SAP implementation from a legacy system.
Furthermore, we have implemented SAP BI to have some reporting on invoice documents (specific needs not covered by ECC6).
Nice (and rich) solution!
Maybe it is the reason why people don not need to use SIS transactions.
Very good reason indeed.
We have planned to change our system in 2 ou 3 years and SAP will become the source of Sales Orders. Maybe users will want to use S001, S003... and other tables at this time.
Or maybe not, in the same way that Billing Document info is now replicated to SAP BI, then it would make sense to also replicate Sales Document and Deliveries to SAP BI in the future.
In general, my Consulting customers do not use the standard infostructures because they do not meet their needs.
New infostructures are created during or after project implementation.
Of course SAP BI is a much better solution, but sometimes small is beautiful
That's why I was wondering if archiving would be a cautious compromise for these tables : if we do have needs to access to the data later, we will be able to view them by SARI.
Not sure if that will be helpful, but will not hurt anyway. If something goes wrong, you would still be able to reconstruct the data in the SIS table anyway.
Concerning SAP BI extractors, my colleagues told me they were using 2LIS_13_VDITM datasource and my question was about an hypothetic link between the SIS tables and this datasource.
My understanding is that this datasource takes data directly from the billing item (VBRP), so it does not care about the information available in the SIS tables.
Best Regards,
Franck Lumpe
Freelance SAP Logistics Consultant

BAPI/Function module TO block material which is mentioned in sales order

Hi All
Is there any BAPI to block material which is mationed in sales order....
I am using BAPI_MATERIAL_AVAILABILITY to check material availibility
how to block quantity if it is available whicl creating sales order via
"BAPI_SALESORDER_CREATEFROMDATA2"
..Thanks

The normal SAP ATP done in the sales orders use the figure ''committed qty'' meaning that if the ATP has been done and confirmed, that quantity will not appear in the next sales order as available.
So if You're using the normal BAPI to create the sales order, the normal ATP function will be called in the processing.
Nevertheless another solution to this issue is to have the MTO (Make-to-order) solution where the requirements are ''attached'' to one sales order/line only.....like this the problem of the stock being taken to another customer disappears.
To do this you'll have to configure the following :
- Go to SPRO and go to Sales and distribution -> Basic functions -> Availability check and transfer of requirements -> Determination of requirements using transaction - Here insert the entry with your sales order type - MRP type (from material master - you might want to consider create one only for this solution) and you should use one of the following:
- KEL Make-to-order, mat. variants
- KELV Make-to-ord.variant + consump
- KP Make-to-order with project
and choose the origin of your requirement - 1 - Item category + MRP Type
- Than configure the association of the requirement type above to the requirement class (normally is the same code) transaction *OVZH*
- Than configure the requirement class (this is what will tell the system the MTO) transaction *OVZG* - On the screen in the field Special stock - E - Sales order stock and please ask for help from an FI consultant because the area of *Account assignment is very important to be well configured*
About the BAPI you're using - Its correct - That's the normal BAPI to be used, taking only into consideration the product allocation issue - MARA-KOSCH
Explaining a little the BAPI you're using :
The program should check if the selected material is allocated or non-allocated.
This information is stored in a field MARA-KOSCH.
We should check this field and if the field is not empty then material is allocated, otherwise is not:
 select kosch into l_kosch
 from mara
 where matnr = <VBAP-MATNR>. " Selected material
 if subrc = 0.
 if l_kosch is initial.
 +" Perform calculation for non-allocated materials+
 else.
 +" Perform calculation for allocated materials+
 endif.
 else.
 " Material not found, skip it ...
 endif.
For allocated materials it will be checked allocation for the netting market of that Order.
The calculation rules for allocated and non-allocated materials are different.
For Non-allocated materials
BAPI 'BAPI_MATERIAL_AVAILABILITY' should be used for getting the ATP quantity.
Bapi should be called as follows --
data: lfl_bapiwmdvs type bapiwmdvs,
lit_bapiwmdvs type standard table of bapiwmdvs,
lfl_bapiwmdve type bapiwmdve,
lit_bapiwmdve type standard table of bapiwmdve,
l_dialogflag type bapicm61v-diafl.
call function 'BAPI_MATERIAL_AVAILABILITY'
exporting
plant = <VBAP-WERKS>
material = <VBAP-MATNR>
unit = <VBAP- VRKME>
check_rule = 'A'
+* STGE_LOC =+
+* BATCH =+
+* CUSTOMER =+
importing
+* ENDLEADTME =+
+* av_qty_plt =+
DIALOGFLAG = l_dialog
+* RETURN =+
tables
wmdvsx = lit_bapiwmdvs
wmdvex = lit_bapiwmdve.
Please note that table lit_bapiwmdvs is the input table and to this following input should be passed -
lfl_bapiwmdvs-req_date = sy-datum. "Current date
lfl_bapiwmdvs- REQ_QTY = <Unconfirmed Quantity> in Sales Order Unit
append lfl_bapiwmdvs to lit_bapiwmdvs.
The return value l_dailog will be --
' ' --- Quantity can be Delivered -- Item to be displayed in the Report!
'X' --- Complete quantity cannot be delivered -- ATP failed, Item not to be displayed.
'N' --- Material not relevant for ATP --- Item not to be displayed in the Report.
For Allocated materials
For the allocated Materials, we have to first do the ATP check in same fashion as for Non-allocated Materials and then in addition to this ATP check, we have to also check for Allocation from SIS table S941.
If ATP check fails, straight away the Item should be ignored from Output display.
If ATP check passes, we further check allocation as follows --
Valid entry should select from S941 as -
data: l_period like s941-spbup,
l_BUPER LIKE T009B-POPER,
l_GJAHR LIKE T009B-BDATJ,
lfl_s941 type t_s941.
data: l_bukrs type tvko-bukrs,
l_periv type t001-periv.
* Select company code
select single bukrs into l_bukrs
from tvko
where vkorg = <VBAK-VKORG>.
* Select fiscal year variant
select single periv into l_periv
from t001
where bukrs = l_bukrs.
* Get Period
CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
EXPORTING
I_DATE = sy-datum
I_PERIV = l_periv
IMPORTING
E_BUPER = l_buper
E_GJAHR = l_gjahr
EXCEPTIONS
INPUT_FALSE = 1
T009_NOTFOUND = 2
T009B_NOTFOUND = 3
OTHERS = 4
IF SY-SUBRC <> 0.
* Ignore entry and skip further processing
ENDIF.
concatenate l_gjahr l_buper+1(2) into l_period.
select single kcqty aemenge from s941
into corresponding fields of lfl_s941
where SPBUP = l_period
and KONOB = 'OBJ_ALL_MATERIALS'
AND MATNR = <VBAP-MATNR>
and zzcnetmark = <VBAK-ZZCNETMARK>
and VRSIO EQ '000'.
IF SY-SUBRC <> 0.
*Ignore entry and skip further processing
ENDIF.
Remaining Allocation = difference between product allocation quantity and incoming order quantity
i.e. (S941-KCQTY - S941-AEMENGE). Now we have to compare this qty with the Unconfirmed qty.
Ensure same Material UOM for quantity comparison as follows --
IF <VBAP-VRKME> NE <S941-BASME>.
CALL FUNCTION 'MD_CONVERT_MATERIAL_UNIT'
EXPORTING
i_matnr = <VBAP-MATNR>
i_in_me = <VBAP-VRKME>
i_out_me = <S941-BASME>
i_menge = <Unconfirmed qty in Sales UOM>
IMPORTING
e_menge = l_menge
EXCEPTIONS
error_in_application = 1
error = 2
OTHERS = 3.
IF sy-subrc <> 0.
* Ignore entry and skip further processing
ENDIF.
ELSE.
*If both Units are same no need for conversion
l_menge = <Unconfirmed qty in Sales UOM>
ENDIF.
Then, compare if Remaining Allocation > = l_menge i.e. Unconfirmed quantity converted to S941-BASME unit, then there is enough allocation for this Material for the Unconfirmed quantity and should be displayed in the report.
Else, the Item should be ignored.

Reg: Error for updating info structure S001

Hi ,
While creating sales order, delivery and purchase order. iam getting the follwing error:
"Error 4 updating info structure S001". Please help me.
Thanks,
Bandi

Hello,
Updates of these reporting tables are done in asynchronous mode.
Check transaction SM13 and try to find back the update of table S001 and analyze the error.
Several OSS-notes explain what can go wrong with updates of LIS and SIS tables like S001.
Wim

How to update SIS Structure S503 table for Sales Order

Hi All,
I have a requirement where i want to restrict S503 table getting updated for an Item Category. Can somebody please help me in this.
Complete scenario:
I am splitting Sales Order line item into multiple Sub Line items based on batch determination. So for a line item 10 in Sales Order having ordered quantity 1000 i have 2 more sub line items 101 and 102 based on 2 available batches having 500 quantites each. When Sales Order is saved S503 have 1 entry for SO created but the ordered and confirmed quantity is doubled as it is picking it from main line item 10 as well as from 101 and 102.
Is there any way to restrict the main line item entry quantity from getting in to SIS structures.
Thanks,
Sudhir.

Hi,
There is a change in the requirement.
Scenario:
I have created a sales order with some 4 condition types, in that 2 condition types are of class A & B and the other two is of class C. Here I need to update the condition price of class A & B only and the remaining condition types should not get update even though there is an updated price is available.
For the above scenario, I need to write a standalone program. Do we have any function modules to update the price of the single condition in the sales order? Please tell me how we can update the sales order at item condition level.
Thanks.
Balaram

CO table growth rate

Hi,
We have gone line with SAP ECC for retail scenario recently. Our database is growing 3 GB per day which includes both data and index growth.
Modules configured:
SD (Retail), MM, HR and FI/CO.
COPA is configured for reporting purpose to find article wise sales details per day and COPA summarization has not been done.
Total sales order created per day on an average: 4000
Total line items of sales order on an average per day: 25000
Total purchase order created per day on an avearage: 1000
Please suggest whether database growth of 3 GB per day is normal for our scenario or should we do something to restrict the database growth.
Fastest Growing tables are,
CE11000     Operating Concern fo
CE31000     Operating Concern fo
ACCTIT     Compressed Data from FI/CO Document
BSIS     Accounting: Secondary Index for G/L Accounts
GLPCA     EC-PCA: Actual Line Items
FAGLFLEXA      General Ledger: Actual Line Items
VBFA     Sales Document Flow
RFBLG     Cluster for accounting document
FAGL_SPLINFO     Splittling Information of Open Items
S120     Sales as per receipts
MSEG     Document Segment: Article
VBRP     Billing Document: Item Data
ACCTCR     Compressed Data from FI/CO Document - Currencies
CE41000_ACCT     Operating Concern fo
S033     Statistics: Movements for Current Stock (Individual Records)
EDIDS     Status Record (IDoc)
CKMI1     Index for Accounting Documents for Article
LIPS     SD document: Delivery: Item data
VBOX     SD Document: Billing Document: Rebate Index
VBPA     Sales Document: Partner
BSAS     Accounting: Secondary Index for G/L Accounts (Cleared Items)
BKPF     Accounting Document Header
FAGL_SPLINFO_VAL     Splitting Information of Open Item Values
VBAP     Sales Document: Item Data
KOCLU     Cluster for conditions in purchasing and sales
COEP     CO Object: Line Items (by Period)
S003     SIS: SalesOrg/DistCh/Division/District/Customer/Product
S124     Customer / article
SRRELROLES     Object Relationship Service: Roles
S001     SIS: Customer Statistics
Is there anyway we can reduce the datagrowth without affecting the functionalities configured?
Is COPA summarization configuration will help reducing the size of the FI/CO tables growth?
Regards,
Nalla.

user480060 wrote:
Dear all,
Oracle 9.2 on AIX 5.3
In one of our database, one table has a very fast growth rate.
How can I check if the table growth is normal or not.
Please advice
The question is, what is a "very fast growth rate"?
What are the DDL of the table resp. the data types that the table uses?
One potential issue could be the way the table is populated: If you constantly insert into the table using a direct-path insert (APPEND hint) and subsequently delete rows then your table will grow faster than required because the deleted rows won't be reused by the direct-path insert because it always writes above the current high-water mark of your table.
May be you want to check your application for such an case if you think that the table grows faster than the actual amount of data it contains.
You could use the ANALYZE command to get information about empty blocks and average free space in the blocks or use the procedures provided by DBMS_SPACE package to find out more about the current usage of your segment.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

Unable to find data in s677 table

Hi I had maintained planned data in md63 for month 1-5 of 2012 but unable to find it in table s677, help.

Hi Allen,
Referring to replies:
1. You entered values directly in MD63
2. No updates in table-S677 or PBIM.
Let me clarify few things.
SIS-S677 is custom info structure (Not a standard SIS) designed to your requirement. That means you're working on S&OP Flexible Planning module.
So as a prerequisite to this module you must maintain below mix of Config & master data:
1. Sales Info Structure i.e. S677 with update groups & rules. To capture any sales history.
2. Planning Type: It's config and Planning type defines the content and the layout of the lines in the planning table.
3. Planning hierarchy: It's a Master data and is a combination of characteristic values based on the characteristics of one information structure.
4. Planning Table: It's the place where a Planning is done.
After all above set-up, you would be able to enter in Planning Table for planning the products.
Steps for Planning/Forecasting:
1. Based on your SIS Update groups & Rules, a S677 will be updated with sales quantities with Version-00 and same will be used to calculate forecast.
2. Using forecast model setup, a forecasting can be run in Planning Table for a particular product.
3. Forecast/planning values then will be saved in Planning Table. Once you save these values & come out of Planning Table, these values will be updated in S677 with version-A00.
4. Then you need to transfer Forecast/Planning values to Demand Management from Planning Table.
5. Check if values can be seen in Demand Management (MD63). If yes, a seperate SAP standard table-PBIM, PBHI etc. will be updated. These values in MD63 are called as Planned Ind Requirement (PIR).
6. Once PIR can be seen in MD63, you can run MRP Run.
7. Once MRP finished, you can go-ahead with further processing.
This is how the complete scenario is. Check if it's okay and then revert if any further issue.
Regards,
Anup

Creating a single context index on a one-to-many and lookup table

Hello,
I've been successfully setting up text indexes on multiple columns on the same table (using MULTI_COLUMN_DATASTORE preferences), but now I have a situation with a one-to-many data collection table (with a FK to a lookup table), and I need to search columns across both of these tables. Sample code below, more of my chattering after the code block:
CREATE TABLE SUBMISSION
( SUBMISSION_ID NUMBER(10) NOT NULL,
SUBMISSION_NAME VARCHAR2(100) NOT NULL
CREATE TABLE ADVISOR_TYPE
( ADVISOR_TYPE_ID NUMBER(10) NOT NULL,
ADVISOR_TYPE_NAME VARCHAR2(50) NOT NULL
CREATE TABLE SUBMISSION_ADVISORS
( SUBMISSION_ADVISORS_ID NUMBER(10) NOT NULL,
SUBMISSION_ID NUMBER(10) NOT NULL,
ADVISOR_TYPE_ID NUMBER(10) NOT NULL,
FIRST_NAME VARCHAR(50) NULL,
LAST_NAME VARCHAR(50) NULL,
SUFFIX VARCHAR(20) NULL
INSERT INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME) VALUES (1, 'Some Research Paper');
INSERT INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME) VALUES (2, 'Thesis on 17th Century Weather Patterns');
INSERT INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME) VALUES (3, 'Statistical Analysis on Sunny Days in March');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (1, 'Department Chair');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (2, 'Department Co-Chair');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (3, 'Professor');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (4, 'Associate Professor');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (5, 'Scientist');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (1,1,2,'John', 'Doe', 'PhD');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (2,1,2,'Jane', 'Doe', 'PhD');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (3,2,3,'Johan', 'Smith', NULL);
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (4,2,4,'Magnus', 'Jackson', 'MS');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (5,3,5,'Williard', 'Forsberg', 'AMS');
COMMIT;I want to be able to create a text index to lump these fields together:
SUBMISSION_ADVISORS.FIRST_NAME
SUBMISSION_ADVISORS.LAST_NAME
SUBMISSION_ADVISORS.SUFFIX
ADVISOR_TYPE.ADVISOR_TYPE_NAME
I've looked at DETAIL_DATASTORE and USER_DATASTORE, but the examples in Oracle Docs for DETAIL_DATASTORE leave me a little bit perplexed. It seems like this should be pretty straightforward.
Ideally, I'm trying to avoid creating new columns, and keeping the trigger adjustments to a minimum. But I'm open to any and all suggestions. Thanks for for your time and thoughts.
-Jamie

I would create a procedure that creates a virtual document with tags, which is what the multi_column_datatstore does behind the scenes. Then I would use that procedure in a user_datastore, so the result is the same for multiple tables as what a multi_column_datastore does for one table. I would also use either auto_section_group or some other type of section group, so that you can search using WITHIN as with the multi_column_datastore. Please see the demonstration below.
SCOTT@orcl_11gR2> -- tables and data that you provided:
SCOTT@orcl_11gR2> CREATE TABLE SUBMISSION
2 ( SUBMISSION_ID NUMBER(10) NOT NULL,
3 SUBMISSION_NAME VARCHAR2(100) NOT NULL
4 )
5 /
Table created.
SCOTT@orcl_11gR2> CREATE TABLE ADVISOR_TYPE
2 ( ADVISOR_TYPE_ID NUMBER(10) NOT NULL,
3 ADVISOR_TYPE_NAME VARCHAR2(50) NOT NULL
4 )
5 /
Table created.
SCOTT@orcl_11gR2> CREATE TABLE SUBMISSION_ADVISORS
2 ( SUBMISSION_ADVISORS_ID NUMBER(10) NOT NULL,
3 SUBMISSION_ID NUMBER(10) NOT NULL,
4 ADVISOR_TYPE_ID NUMBER(10) NOT NULL,
5 FIRST_NAME VARCHAR(50) NULL,
6 LAST_NAME VARCHAR(50) NULL,
7 SUFFIX VARCHAR(20) NULL
8 )
9 /
Table created.
SCOTT@orcl_11gR2> INSERT ALL
2 INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME)
3 VALUES (1, 'Some Research Paper')
4 INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME)
5 VALUES (2, 'Thesis on 17th Century Weather Patterns')
6 INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME)
7 VALUES (3, 'Statistical Analysis on Sunny Days in March')
8 SELECT * FROM DUAL
9 /
3 rows created.
SCOTT@orcl_11gR2> INSERT ALL
2 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
3 VALUES (1, 'Department Chair')
4 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
5 VALUES (2, 'Department Co-Chair')
6 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
7 VALUES (3, 'Professor')
8 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
9 VALUES (4, 'Associate Professor')
10 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
11 VALUES (5, 'Scientist')
12 SELECT * FROM DUAL
13 /
5 rows created.
SCOTT@orcl_11gR2> INSERT ALL
2 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
3 VALUES (1,1,2,'John', 'Doe', 'PhD')
4 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
5 VALUES (2,1,2,'Jane', 'Doe', 'PhD')
6 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
7 VALUES (3,2,3,'Johan', 'Smith', NULL)
8 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
9 VALUES (4,2,4,'Magnus', 'Jackson', 'MS')
10 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
11 VALUES (5,3,5,'Williard', 'Forsberg', 'AMS')
12 SELECT * FROM DUAL
13 /
5 rows created.
SCOTT@orcl_11gR2> -- constraints presumed based on your description:
SCOTT@orcl_11gR2> ALTER TABLE submission ADD CONSTRAINT submission_id_pk
2 PRIMARY KEY (submission_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE advisor_type ADD CONSTRAINT advisor_type_id_pk
2 PRIMARY KEY (advisor_type_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD CONSTRAINT submission_advisors_id_pk
2 PRIMARY KEY (submission_advisors_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD CONSTRAINT submission_id_fk
2 FOREIGN KEY (submission_id) REFERENCES submission (submission_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD CONSTRAINT advisor_type_id_fk
2 FOREIGN KEY (advisor_type_id) REFERENCES advisor_type (advisor_type_id)
3 /
Table altered.
SCOTT@orcl_11gR2> -- resulting data:
SCOTT@orcl_11gR2> COLUMN submission_name FORMAT A45
SCOTT@orcl_11gR2> COLUMN advisor FORMAT A40
SCOTT@orcl_11gR2> SELECT s.submission_name,
2 a.advisor_type_name || ' ' ||
3 sa.first_name || ' ' ||
4 sa.last_name || ' ' ||
5 sa.suffix AS advisor
6 FROM submission_advisors sa,
7 submission s,
8 advisor_type a
9 WHERE sa.advisor_type_id = a.advisor_type_id
10 AND sa.submission_id = s.submission_id
11 /
SUBMISSION_NAME ADVISOR
Some Research Paper Department Co-Chair John Doe PhD
Some Research Paper Department Co-Chair Jane Doe PhD
Thesis on 17th Century Weather Patterns Professor Johan Smith
Thesis on 17th Century Weather Patterns Associate Professor Magnus Jackson MS
Statistical Analysis on Sunny Days in March Scientist Williard Forsberg AMS
5 rows selected.
SCOTT@orcl_11gR2> -- procedure to create virtual documents:
SCOTT@orcl_11gR2> CREATE OR REPLACE PROCEDURE submission_advisors_proc
2 (p_rowid IN ROWID,
3 p_clob IN OUT NOCOPY CLOB)
4 AS
5 BEGIN
6 FOR r1 IN
7 (SELECT *
8 FROM submission_advisors
9 WHERE ROWID = p_rowid)
10 LOOP
11 IF r1.first_name IS NOT NULL THEN
12 DBMS_LOB.WRITEAPPEND (p_clob, 12, '<first_name>');
13 DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r1.first_name), r1.first_name);
14 DBMS_LOB.WRITEAPPEND (p_clob, 13, '</first_name>');
15 END IF;
16 IF r1.last_name IS NOT NULL THEN
17 DBMS_LOB.WRITEAPPEND (p_clob, 11, '<last_name>');
18 DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r1.last_name), r1.last_name);
19 DBMS_LOB.WRITEAPPEND (p_clob, 12, '</last_name>');
20 END IF;
21 IF r1.suffix IS NOT NULL THEN
22 DBMS_LOB.WRITEAPPEND (p_clob, 8, '<suffix>');
23 DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r1.suffix), r1.suffix);
24 DBMS_LOB.WRITEAPPEND (p_clob, 9, '</suffix>');
25 END IF;
26 FOR r2 IN
27 (SELECT *
28 FROM submission
29 WHERE submission_id = r1.submission_id)
30 LOOP
31 DBMS_LOB.WRITEAPPEND (p_clob, 17, '<submission_name>');
32 DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r2.submission_name), r2.submission_name);
33 DBMS_LOB.WRITEAPPEND (p_clob, 18, '</submission_name>');
34 END LOOP;
35 FOR r3 IN
36 (SELECT *
37 FROM advisor_type
38 WHERE advisor_type_id = r1.advisor_type_id)
39 LOOP
40 DBMS_LOB.WRITEAPPEND (p_clob, 19, '<advisor_type_name>');
41 DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r3.advisor_type_name), r3.advisor_type_name);
42 DBMS_LOB.WRITEAPPEND (p_clob, 20, '</advisor_type_name>');
43 END LOOP;
44 END LOOP;
45 END submission_advisors_proc;
46 /
Procedure created.
SCOTT@orcl_11gR2> SHOW ERRORS
No errors.
SCOTT@orcl_11gR2> -- examples of virtual documents that procedure creates:
SCOTT@orcl_11gR2> DECLARE
2 v_clob CLOB := EMPTY_CLOB();
3 BEGIN
4 FOR r IN
5 (SELECT ROWID rid FROM submission_advisors)
6 LOOP
7 DBMS_LOB.CREATETEMPORARY (v_clob, TRUE);
8 submission_advisors_proc (r.rid, v_clob);
9 DBMS_OUTPUT.PUT_LINE (v_clob);
10 DBMS_LOB.FREETEMPORARY (v_clob);
11 END LOOP;
12 END;
13 /
<first_name>John</first_name><last_name>Doe</last_name><suffix>PhD</suffix><submission_name>Some
Research Paper</submission_name><advisor_type_name>Department Co-Chair</advisor_type_name>
<first_name>Jane</first_name><last_name>Doe</last_name><suffix>PhD</suffix><submission_name>Some
Research Paper</submission_name><advisor_type_name>Department Co-Chair</advisor_type_name>
<first_name>Johan</first_name><last_name>Smith</last_name><submission_name>Thesis on 17th Century
Weather Patterns</submission_name><advisor_type_name>Professor</advisor_type_name>
<first_name>Magnus</first_name><last_name>Jackson</last_name><suffix>MS</suffix><submission_name>The
sis on 17th Century Weather Patterns</submission_name><advisor_type_name>Associate
Professor</advisor_type_name>
<first_name>Williard</first_name><last_name>Forsberg</last_name><suffix>AMS</suffix><submission_name
Statistical Analysis on Sunny Days inMarch</submission_name><advisor_type_name>Scientist</advisor_type_name>
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> -- user_datastore that uses procedure:
SCOTT@orcl_11gR2> BEGIN
2 CTX_DDL.CREATE_PREFERENCE ('sa_datastore', 'USER_DATASTORE');
3 CTX_DDL.SET_ATTRIBUTE ('sa_datastore', 'PROCEDURE', 'submission_advisors_proc');
4 END;
5 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> -- index (on optional extra column) that uses user_datastore and section group:
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD (any_column VARCHAR2(1))
2 /
Table altered.
SCOTT@orcl_11gR2> CREATE INDEX submission_advisors_idx
2 ON submission_advisors (any_column)
3 INDEXTYPE IS CTXSYS.CONTEXT
4 PARAMETERS
5 ('DATASTORE sa_datastore
6 SECTION GROUP CTXSYS.AUTO_SECTION_GROUP')
7 /
Index created.
SCOTT@orcl_11gR2> -- what is tokenized, indexed, and searchable:
SCOTT@orcl_11gR2> SELECT token_text FROM dr$submission_advisors_idx$i
2 /
TOKEN_TEXT
17TH
ADVISOR_TYPE_NAME
AMS
ANALYSIS
ASSOCIATE
CENTURY
CHAIR
CO
DAYS
DEPARTMENT
DOE
FIRST_NAME
FORSBERG
JACKSON
JANE
JOHAN
JOHN
LAST_NAME
MAGNUS
MARCH
PAPER
PATTERNS
PHD
PROFESSOR
RESEARCH
SCIENTIST
SMITH
STATISTICAL
SUBMISSION_NAME
SUFFIX
SUNNY
THESIS
WEATHER
WILLIARD
34 rows selected.
SCOTT@orcl_11gR2> -- sample searches across all data:
SCOTT@orcl_11gR2> VARIABLE search_string VARCHAR2(100)
SCOTT@orcl_11gR2> EXEC :search_string := 'professor'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2 a.advisor_type_name || ' ' ||
3 sa.first_name || ' ' ||
4 sa.last_name || ' ' ||
5 sa.suffix AS advisor
6 FROM submission_advisors sa,
7 submission s,
8 advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string) > 0
10 AND sa.advisor_type_id = a.advisor_type_id
11 AND sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME ADVISOR
Thesis on 17th Century Weather Patterns Professor Johan Smith
Thesis on 17th Century Weather Patterns Associate Professor Magnus Jackson MS
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'doe'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> /
SUBMISSION_NAME ADVISOR
Some Research Paper Department Co-Chair John Doe PhD
Some Research Paper Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'paper'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> /
SUBMISSION_NAME ADVISOR
Some Research Paper Department Co-Chair John Doe PhD
Some Research Paper Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> -- sample searches within specific columns:
SCOTT@orcl_11gR2> EXEC :search_string := 'chair'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2 a.advisor_type_name || ' ' ||
3 sa.first_name || ' ' ||
4 sa.last_name || ' ' ||
5 sa.suffix AS advisor
6 FROM submission_advisors sa,
7 submission s,
8 advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string || ' WITHIN advisor_type_name') > 0
10 AND sa.advisor_type_id = a.advisor_type_id
11 AND sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME ADVISOR
Some Research Paper Department Co-Chair John Doe PhD
Some Research Paper Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'phd'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2 a.advisor_type_name || ' ' ||
3 sa.first_name || ' ' ||
4 sa.last_name || ' ' ||
5 sa.suffix AS advisor
6 FROM submission_advisors sa,
7 submission s,
8 advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string || ' WITHIN suffix') > 0
10 AND sa.advisor_type_id = a.advisor_type_id
11 AND sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME ADVISOR
Some Research Paper Department Co-Chair John Doe PhD
Some Research Paper Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'weather'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2 a.advisor_type_name || ' ' ||
3 sa.first_name || ' ' ||
4 sa.last_name || ' ' ||
5 sa.suffix AS advisor
6 FROM submission_advisors sa,
7 submission s,
8 advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string || ' WITHIN submission_name') > 0
10 AND sa.advisor_type_id = a.advisor_type_id
11 AND sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME ADVISOR
Thesis on 17th Century Weather Patterns Professor Johan Smith
Thesis on 17th Century Weather Patterns Associate Professor Magnus Jackson MS
2 rows selected.

What are the fileds and table names for salesorder reoprt

hi,
how to find tables and fields for the sales order report / any report?

Hi,
Check the following standard reports in SD,
Sales summary - VC/2
Display Customer Hierarchy - VDH2
Display Condition record report - V/I6
Pricing Report - V/LD
Create Net Price List - V_NL
List customer material info - VD59
List of sales order - VA05
List of Billing documents - VF05
Inquiries list - VA15
Quotation List - VA25
Incomplete Sales orders - V.02
Backorders - V.15
Outbound Delivery Monitor - VL06o
Incomplete delivery - V_UC
Customer Returns-Analysis - MC+A
Customer Analysis- Sales - MC+E
Customer Analysis- Cr. Memo - MC+I
Deliveries-Due list - VL04
Billing due list - VF04
Incomplete Billing documents - MCV9
Customer Analysis-Basic List - MCTA
Material Analysis(SIS) - MCTC
Sales org analysis - MCTE
Sales org analysis-Invoiced sales - MC+2
Material Analysis-Incoming orders - MC(E
General- List of Outbound deliveries - VL06f
Material Returns-Analysis - MC+M
Material Analysis- Invoiced Sales - MC+Q
Variant configuration Analysis - MC(B
Sales org analysis-Incoming orders - MC(I
Sales org analysis-Returns - MC+Y
Sales office Analysis- Invoiced Sales - MC-E
Sales office Analysis- Returns - MC-A
Shipping point Analysis - MC(U
Shipping point Analysis-Returns - MC-O
Blocked orders - V.14
Order Within time period - SD01
Duplicate Sales orders in period - SDD1
Display Delivery Changes - VL22
Reward if helpful.

SELECT on XML DB Table works for Schema owner, not for Schema user

Hi,
We are working on Oracle 10.2.0.3 under HP-UX.
We get ORA-01031: Insufficient Privileges when trying to execute Query
on Oracle XMLDB Table by Schema User
Here are detailed steps:
1) We have 2 users: CDROWNER (Schema Owner)
CDRJAVA (Schema User)
2) login as CDROWNER and execute following:
3) Register 2 XSDs (Common is used by CorridorRate)
Common.xsd:
<?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
 <xsd:complexType name="NamedCustomer_V1" xdb:SQLType="NAMED_CUSTOMER_T">
 <xsd:annotation>
 <xsd:documentation>Named customer for the quote</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="SAP_IDS" type="SAPIDCollection_V1" minOccurs="0" xdb:SQLName="SAP_IDS">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="BookingConditions" type="xsd:string" minOccurs="0" xdb:SQLName="BOOKING_CONDITIONS"/>
 <xsd:element name="BLConditions" type="xsd:int" xdb:SQLName="BL_CONDITIONS"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="Attachment_V1" xdb:SQLType="ATTACHMENT_T">
 <xsd:annotation>
 <xsd:documentation>Quote attachment</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Url" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_URL"/>
 <xsd:element name="Text" type="xsd:string" minOccurs="0" xdb:SQLName="ATTACH_TEXT"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="SentOfferingRecord_V1" xdb:SQLType="SENT_OFFERING_RECORD_T">
 <xsd:annotation>
 <xsd:documentation>Record of quote sending out to customer</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="TimeSent" type="xsd:string" minOccurs="0" xdb:SQLName="TIME_SENT"/>
 <xsd:element name="UserName" type="xsd:string" minOccurs="0" xdb:SQLName="USER_NAME"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="QuoteFormatSettings_V1" xdb:SQLType="QUOTE_FMT_SETTINGS_T">
 <xsd:annotation>
 <xsd:documentation>Quote format setting specification</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="TemplateName" type="xsd:string" minOccurs="0" xdb:SQLName="TEMPLATE_NAME">
 <xsd:annotation>
 <xsd:documentation>predefined format template</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="OptionalContentIDs" type="StringWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="OPTIONAL_CONTENTS" xdb:SQLCollType="OPTIONAL_CONTENT_V">
 <xsd:annotation>
 <xsd:documentation>optional contents</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="StandardRemarkIDs" type="IDWrapper_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="STANDARD_REMARKS" xdb:SQLCollType="STANDARD_REMARK_V">
 <xsd:annotation>
 <xsd:documentation>standard remarks specified by each region/office</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="StandardDisclaimerID" type="ID_LongNumeric_V1" minOccurs="0" xdb:SQLName="STANDARD_DISCLAIMER">
 <xsd:annotation>
 <xsd:documentation>standard disclaimer specified by each region/office</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="ShowSurcharges" type="ShowSurchargeType_V1" xdb:SQLName="SHOW_SURCHARGES">
 <xsd:annotation>
 <xsd:documentation>specifies how surcharges are shown in the offering document, can be show prepaid only, collect only or all</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:simpleType name="SurchargeCode_V1">
 <xsd:restriction base="xsd:string"/>
 </xsd:simpleType>
 <xsd:simpleType name="ShowSurchargeType_V1">
 <xsd:annotation>
 <xsd:documentation>Indicator for quote to show prepaid, collect or all surcharges</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="Prepaid"/>
 <xsd:enumeration value="Collect"/>
 <xsd:enumeration value="All"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:complexType name="StandardRemarkAndDisclaimer_V1" xdb:SQLType="STD_REMARK_AND_DISCLAIMER_T">
 <xsd:annotation>
 <xsd:documentation>Region specific standard remark and disclaimer</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Id" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_ID"/>
 <xsd:element name="Region" type="xsd:string" minOccurs="0" xdb:SQLName="STD_REMARK_REGION"/>
 <xsd:element name="IsRemark" type="xsd:boolean" xdb:SQLName="IS_REMARK"/>
 </xsd:sequence>
 </xsd:complexType>
 
 
 
 
 
 <xsd:complexType name="GeoIDCollection_V1" xdb:SQLType="GEO_ID_COLLECTION_T">
 <xsd:sequence>
 <xsd:element name="IDWrappers" type="IDWrapper_V1" maxOccurs="unbounded" xdb:SQLName="GEO_ID_WRAPPERS" xdb:SQLCollType="GEO_ID_WRAPPER_V"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="IDWrapper_V1" xdb:SQLType="ID_WRAPPER_T">
 <xsd:sequence>
 <xsd:element name="Value" type="ID_LongNumeric_V1" xdb:SQLName="ID_VAL"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="OfficeCodeCollection_V1" xdb:SQLType="OFFICE_CODE_COLLECTION_T">
 <xsd:sequence>
 <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="OFFICE_CODE_V"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="SAPIDCollection_V1" xdb:SQLType="SAP_ID_COLLECTION_T">
 <xsd:sequence>
 <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SAP_ID_V"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="ServiceLoopCodeCollection_V1" xdb:SQLType="SERVICE_LOOP_CODE_COLLECTION_T">
 <xsd:sequence>
 <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="SERVICE_LOOP_CODE_V"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="IncludedHSCodeCollection_V1" xdb:SQLType="INCLUDED_HS_CODE_COLLECTION_T">
 <xsd:sequence>
 <xsd:element name="StringWrappers" type="StringWrapper_V1" maxOccurs="unbounded" xdb:SQLName="STRING_WRAPPERS" xdb:SQLCollType="INCLUDED_HS_CODE_V"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="StringWrapper_V1" xdb:SQLType="STRING_WRAPPER_T">
 <xsd:sequence>
 <xsd:element name="Value" xdb:SQLName="STR_VAL">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="256"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 
 <xsd:complexType name="GuidelineRateReference_V1">
 <xsd:annotation>
 <xsd:documentation>Represents a guideline rate containing an ocean rate and up to 4 inland/port arbitrary add-on rates</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="OutboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>The first outbound inland rate. If present, the location of this rate is always the point of receipt. Otherwise the point of receipt is (one of) the Trunk origin(s). The over location must match with either OB2 Location or Trunk Origin (if OB2 is not present)</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="OutboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>An optional outbound inland rate. If present, the location must match with the over location of OB1 and the over location of this rate must match with the origin of the Trunk.</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="BaseRateID" type="ID_LongNumeric_V1">
 <xsd:annotation>
 <xsd:documentation>The BaseRate = trunk / ocean rate.</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="InboundInlandRate1ID" type="ID_LongNumeric_V1" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>The inbound rate connecting to the destination of the trunk. If there is only one inbound rate (IB2 is not present), then this rate will have the final destination. </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="InboundInlandRate2ID" type="ID_LongNumeric_V1" minOccurs="0">
 <xsd:annotation>
 <xsd:documentation>A second inbound rate which connects to the first inbound rate to arrive at a final destination.</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 
 <xsd:simpleType name="AgreementID_V1">
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="AgreementStatus_V1">
 <xsd:annotation>
 <xsd:documentation>Agreement Status, like filed, approve, terminated, amend</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20"/>
 <xsd:enumeration value="File"/>
 <xsd:enumeration value="Filed"/>
 <xsd:enumeration value="Approve"/>
 <xsd:enumeration value="Terminated"/>
 <xsd:enumeration value="New"/>
 <xsd:enumeration value="Incomplete"/>
 <xsd:enumeration value="Amend"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="AgreementType_V1">
 <xsd:annotation>
 <xsd:documentation>Agreement type, like CSO, SC, AB</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="3"/>
 <xsd:enumeration value="CSO">
 <xsd:annotation>
 <xsd:documentation>Customized Service Offering</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="RA">
 <xsd:annotation>
 <xsd:documentation>Rate Agreement</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="SVC">
 <xsd:annotation>
 <xsd:documentation>Service Agreement</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="SUR">
 <xsd:annotation>
 <xsd:documentation>Surcharge Agreement</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="SC">
 <xsd:annotation>
 <xsd:documentation>Service Contract</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="TSO">
 <xsd:annotation>
 <xsd:documentation>Territorial Customized Service Offering</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="TSA">
 <xsd:annotation>
 <xsd:documentation>Territorial Service Agreement</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="AB">
 <xsd:annotation>
 <xsd:documentation>Agreement Builder</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="TradeTerm_V1">
 <xsd:annotation>
 <xsd:documentation>Trade term</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="10"/>
 <xsd:enumeration value="FOB"/>
 <xsd:enumeration value="CIF"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="ABDateTime_V1">
 <xsd:restriction base="xsd:dateTime"/>
 </xsd:simpleType>
 
 <xsd:complexType name="PersonName_V1" xdb:SQLType="PERSON_NAME_T">
 <xsd:sequence>
 <xsd:element name="FirstName" minOccurs="0" xdb:SQLName="FIRST_NAME">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string"/>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="LastName" minOccurs="0" xdb:SQLName="LAST_NAME">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string"/>
 </xsd:simpleType>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 
 <xsd:complexType name="EmailAddress_V1" xdb:SQLType="EMAIL_ADDRESS_T">
 <xsd:sequence>
 <xsd:annotation>
 <xsd:documentation>
 A common Type for EmailAddress.
 </xsd:documentation>
 </xsd:annotation>
 <xsd:element name="EmailID" type="xsd:string" xdb:SQLName="EMAIL_ID"/>
 <xsd:element name="EmailType" type="EmailType_V1" default="Unspecified" xdb:SQLName="EMAIL_TYPE"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:simpleType name="EmailType_V1">
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="Home"/>
 <xsd:enumeration value="Work"/>
 <xsd:enumeration value="Unspecified"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="PhoneNumberType_V1">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 Type refers to the contact number type associated to the contact number.
 May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified.
 </xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="BusinessPhone"/>
 <xsd:enumeration value="HomePhone"/>
 <xsd:enumeration value="BusinessFax"/>
 <xsd:enumeration value="HomeFax"/>
 <xsd:enumeration value="MobilePhone"/>
 <xsd:enumeration value="Pager"/>
 <xsd:enumeration value="Telex"/>
 <xsd:enumeration value="Unspecified"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:complexType name="PhoneNumber_V1" xdb:SQLType="PHONE_NUMBER_T">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 PhoneNumber is a common type that defines generic structure of a phone number object.
 </xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="CountryCode" type="xsd:string" minOccurs="0" xdb:SQLName="COUNTRY_CODE">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 CountryCode holds on the country code value.
 </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="AreaCode" type="xsd:string" minOccurs="0" xdb:SQLName="AREA_CODE">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 AreaCode holds on the area code value.
 </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Number" type="xsd:string" xdb:SQLName="PHONE_NUMBER">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 Number holds on the number value.
 </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Extension" type="xsd:string" minOccurs="0" xdb:SQLName="PHONE_EXTN">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 Extension holds on the phone number extension, if applicable
 </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Type" type="PhoneNumberType_V1" default="Unspecified" xdb:SQLName="PHONE_NUM_TYPE">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 Type refers to the contact number type associated to the contact number.
 May include: Business Phone/Fax, Home Phone/Fax, Mobile Phone, Pager, Telex or Unspecified
 Default value is Unspecified.
 </xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 
 <xsd:complexType name="ContactInformation_V1" xdb:SQLType="CONTACT_INFORMATION_T">
 <xsd:sequence>
 <xsd:element name="Name" type="PersonName_V1" minOccurs="0" xdb:SQLName="CONTACT_NAME"/>
 <xsd:element name="EmailAddresses" type="EmailAddress_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="EMAIL_ADDRESSES" xdb:SQLCollType="EMAIL_ADDRESS_V"/>
 <xsd:element name="PhoneNumbers" type="PhoneNumber_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="PHONE_NUMBERS" xdb:SQLCollType="PHONE_NUMBER_V"/>
 </xsd:sequence>
 </xsd:complexType>
 
 <xsd:simpleType name="CardinalDirectionName_V1">
 <xsd:annotation>
 <xsd:documentation>A list of voyage name direction.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="North"/>
 <xsd:enumeration value="South"/>
 <xsd:enumeration value="East"/>
 <xsd:enumeration value="West"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="ID_LongNumeric_V1">
 <xsd:annotation>
 <xsd:documentation>Represents Identifier using long as the restriction - with max - 15 digits</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:long"/>
 </xsd:simpleType>
 
 <xsd:simpleType name="ServiceLoopCode_V1">
 <xsd:annotation>
 <xsd:documentation>A simple type that holds on to the service loop code.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="4"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="CurrencyCode_V1">
 <xsd:annotation>
 <xsd:documentation>A 3 digit currency code string (like USD)</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:length value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="TariffCode_V1">
 <xsd:annotation>
 <xsd:documentation>tariff code that uniquely identify a tariff</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:length value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="Global_UUID_V1">
 <xsd:annotation>
 <xsd:documentation>This is to represent the largest UUID format in the domain. Max. length is 36.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="36"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="UUID_V1">
 <xsd:annotation>
 <xsd:documentation>A system generated uuid in string format. Max. length is 20.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="Global_UUID_V1">
 <xsd:maxLength value="20"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="CustomerContactRoleType_V1">
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="20"/>
 <xsd:enumeration value="Accounting"/>
 <xsd:enumeration value="Booking"/>
 <xsd:enumeration value="Booking_CS"/>
 <xsd:enumeration value="Documentation"/>
 <xsd:enumeration value="General"/>
 <xsd:enumeration value="Operations"/>
 <xsd:enumeration value="Pricing"/>
 <xsd:enumeration value="Sales"/>
 <xsd:enumeration value="Sales_SMM"/>
 <xsd:enumeration value="Warehouse"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="TradeCode_V1">
 <xsd:annotation>
 <xsd:documentation>A simple type that holds on to the trade code.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="ShipmentBoundCode_V1">
 <xsd:annotation>
 <xsd:documentation>A list of shipment bound code.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:enumeration value="IB"/>
 <xsd:enumeration value="OB"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:complexType name="CustomerContactSpecification_V1" xdb:SQLType="CUST_CONTACT_SPEC_T">
 <xsd:sequence>
 <xsd:element name="ContactSpecUUID" type="UUID_V1" xdb:SQLName="CONTACT_SPEC_UUID"/>
 <xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
 <xsd:element name="Role" type="CustomerContactRoleType_V1" xdb:SQLName="CONTACT_ROLE"/>
 <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="CUST_SAP_ID"/>
 <xsd:element name="TradeCode" type="TradeCode_V1" minOccurs="0" xdb:SQLName="TRADE_CODE"/>
 <xsd:element name="TradeLaneCode" type="TradeLaneCode_V1" minOccurs="0" xdb:SQLName="TRADE_LANE_CODE"/>
 <xsd:element name="ServiceLoopCode" type="ServiceLoopCode_V1" minOccurs="0" xdb:SQLName="SERVICE_LOOP_CODE"/>
 <xsd:element name="ShipmentBoundCode" type="ShipmentBoundCode_V1" minOccurs="0" xdb:SQLName="SHIPMENT_BOUND_CODE"/>
 <xsd:element name="CommodityGroupCode" type="AlphaCode_V1" minOccurs="0" xdb:SQLName="COMMODITY_GROUP_CODE"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="CustomerContact_V1" xdb:SQLType="CUSTOMER_CONTACT_T">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 This defines a contact for a Customer. A customer contact is someone to whom an OOCL sales representative communicates regarding business transactions between OOCL and the Customer.
 </xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="ContactUUID" type="UUID_V1" xdb:SQLName="CONTACT_UUID"/>
 <xsd:element name="ContactInformation" type="ContactInformation_V1" xdb:SQLName="CONTACT_INFORMATION"/>
 <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID"/>
 <xsd:element name="Title" minOccurs="0" xdb:SQLName="TITLE">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="35"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="JobTitle" minOccurs="0" xdb:SQLName="JOB_TITLE">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="35"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Department" minOccurs="0" xdb:SQLName="DEPARTMENT">
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="35"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="Specifications" type="CustomerContactSpecification_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="CUST_CONTACT_SPECS" xdb:SQLCollType="CUST_CONTACT_SPEC_V"/>
 </xsd:sequence>
 </xsd:complexType>
 
 <xsd:simpleType name="TradeLaneCode_V1">
 <xsd:annotation>
 <xsd:documentation>A simple type that holds on to the trade lane code.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="CompanyName_V1">
 <xsd:annotation>
 <xsd:documentation>Name of a Company
This is used to denote the information about an organization which may not be a Customer</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="105"/>
 <xsd:minLength value="1"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:complexType name="CorridorBaseRate_V1" xdb:SQLType="CORRIDOR_BASE_RATE_T">
 <xsd:annotation>
 <xsd:documentation>Corridor base rate specifications</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
 <xsd:annotation>
 <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Amount" type="xsd:decimal" minOccurs="0" xdb:SQLName="BASE_RATE_AMOUNT">
 <xsd:annotation>
 <xsd:documentation>charge amount</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Currency" type="CurrencyCode_V1" minOccurs="0" xdb:SQLName="BASE_RATE_CURRENCY">
 <xsd:annotation>
 <xsd:documentation>charge currency code</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="OfferType" minOccurs="0" xdb:SQLName="OFFER_TYPE">
 <xsd:annotation>
 <xsd:documentation>offer type: either OOCL offered or customer requested</xsd:documentation>
 </xsd:annotation>
 <xsd:simpleType>
 <xsd:restriction base="xsd:string">
 <xsd:length value="4"/>
 </xsd:restriction>
 </xsd:simpleType>
 </xsd:element>
 <xsd:element name="IsSOC" type="xsd:boolean" minOccurs="0" xdb:SQLName="IS_SOC">
 <xsd:annotation>
 <xsd:documentation>indicator for shipper owned container</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="EffectiveFrom" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_FROM" xdb:SQLType="TIMESTAMP">
 <xsd:annotation>
 <xsd:documentation>effectime start time of the rate</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="EffectiveTo" type="ABDateTime_V1" minOccurs="0" xdb:SQLName="EFFECTIVE_TO" xdb:SQLType="TIMESTAMP">
 <xsd:annotation>
 <xsd:documentation>effectime end time of the rate</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="TransitTime" type="xsd:string" minOccurs="0" xdb:SQLName="TRANSIT_TIME">
 <xsd:annotation>
 <xsd:documentation>transit time of shipment that the rate offered</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:simpleType name="SAP_ID_V1">
 <xsd:annotation>
 <xsd:documentation xml:lang="en">
 SAP ID is the unique identifier for a given Customer in reference to SAP Application.
 </xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="10"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:complexType name="ABShippingParty_V1" xdb:SQLType="AB_SHIPPING_PARTY_T">
 <xsd:annotation>
 <xsd:documentation>Customer's roles in a shipment, like shipper, consignee, etc</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="CustomerHolder" type="CustomerHolder_V1" xdb:SQLName="CUSTOMER_HOLDER"/>
 <xsd:element name="ShippingRoleGroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="SHIPPING_ROLE_GROUP_ID"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="CustomerHolder_V1" xdb:SQLType="CUSTOMER_HOLDER_T">
 <xsd:annotation>
 <xsd:documentation>A place holder where a new customer was created or modified in agreement builder</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="SAP_ID" type="SAP_ID_V1" minOccurs="0" xdb:SQLName="SAP_ID">
 <xsd:annotation>
 <xsd:documentation>Customer SapID if it is an existing customer</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Name" type="CompanyName_V1" minOccurs="0" xdb:SQLName="COMPANY_NAME">
 <xsd:annotation>
 <xsd:documentation>New customer name that is created during agreement builder creation(customer does not exist in NewCPF)</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="ModifiedContacts" type="CustomerContact_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="MODIFIED_CONTACTS" xdb:SQLCollType="MODIFIED_CONTACT_V"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="ShippingPartyRoleGroup_V1" xdb:SQLType="SHIPPING_PARTY_ROLE_GROUP_T">
 <xsd:annotation>
 <xsd:documentation>All customer's shipping role in an agreement</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="GroupID" type="ID_Integer_V1" minOccurs="0" xdb:SQLName="GROUP_ID"/>
 <xsd:element name="IsShipper" type="xsd:boolean" xdb:SQLName="IS_SHIPPER"/>
 <xsd:element name="IsConsignee" type="xsd:boolean" xdb:SQLName="IS_CONSIGNEE"/>
 <xsd:element name="IsForwarder" type="xsd:boolean" xdb:SQLName="IS_FORWARDER"/>
 <xsd:element name="IsControlParty" type="xsd:boolean" xdb:SQLName="IS_CONTROL_PARTY"/>
 <xsd:element name="IsSignatureParty" type="xsd:boolean" xdb:SQLName="IS_SIGNATURE_PARTY"/>
 <xsd:element name="IsNotifyParty" type="xsd:boolean" xdb:SQLName="IS_NOTIFY_PARTY"/>
 <xsd:element name="IsAssociate" type="xsd:boolean" xdb:SQLName="IS_ASSOCIATE"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:simpleType name="AlphaCode_V1">
 <xsd:annotation>
 <xsd:documentation>Code of a CommodityReportGroup. The Business Community refers to this 3 digit code as the AlphaCode
 </xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="3"/>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="CargoNatureCode_V1">
 <xsd:annotation>
 <xsd:documentation>The classification code of cargo for special stowage arrangement</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="2"/>
 <xsd:enumeration value="AW">
 <xsd:annotation>
 <xsd:documentation>Awkward</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="DG">
 <xsd:annotation>
 <xsd:documentation>Dangerous</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="GC">
 <xsd:annotation>
 <xsd:documentation>GeneralCargo</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 <xsd:enumeration value="RF">
 <xsd:annotation>
 <xsd:documentation>Reefer</xsd:documentation>
 </xsd:annotation>
 </xsd:enumeration>
 </xsd:restriction>
 </xsd:simpleType>
 <xsd:simpleType name="ID_Integer_V1">
 <xsd:annotation>
 <xsd:documentation>Represents Identifier using Integer as the restriction.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:int"/>
 </xsd:simpleType>
 <xsd:complexType name="CorridorVolume_V1" xdb:SQLType="CORRIDOR_VOLUME_T">
 <xsd:annotation>
 <xsd:documentation>Corridor volumns associated with corridor base rate</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="ID" type="xsd:int" xdb:SQLName="IDNUM">
 <xsd:annotation>
 <xsd:documentation>A numeric identifier which identifies a CorridorVolume only in the context of a Quote/Agreement</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
 <xsd:annotation>
 <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
 <xsd:annotation>
 <xsd:documentation>corridor rate volume specification</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="VolumePatterns" type="VolumePattern_V1" minOccurs="0" maxOccurs="unbounded" xdb:SQLName="VOLUME_PATTERNS" xdb:SQLCollType="VOLUME_PATTERN_V">
 <xsd:annotation>
 <xsd:documentation>detailed volume sepecification</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Basis" type="xsd:string" minOccurs="0" xdb:SQLName="BASIS"/>
 <xsd:element name="IsConditionOfRate" type="xsd:boolean" xdb:SQLName="IS_CONDITION_OF_RATE">
 <xsd:annotation>
 <xsd:documentation>indicate if the volume sepecification is a condition of the corridor rate</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="IsShared" type="xsd:boolean" xdb:SQLName="IS_SHARED">
 <xsd:annotation>
 <xsd:documentation>Indicates if the volume group is shared by more than one corridor rate. When true, sizetype should be null</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="IsForEntireAgreement" type="xsd:boolean" xdb:SQLName="IS_FOR_AGREEMENT"/>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="VolumePattern_V1" xdb:SQLType="VOLUME_PATTERN_T">
 <xsd:annotation>
 <xsd:documentation>Agreement volume pattern</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Volume" type="ShipmentVolume_V1" minOccurs="0" xdb:SQLName="VOLUME">
 <xsd:annotation>
 <xsd:documentation>volume amount</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="Period" type="xsd:string" minOccurs="0" xdb:SQLName="PERIOD">
 <xsd:annotation>
 <xsd:documentation>time period for the volume</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 </xsd:sequence>
 </xsd:complexType>
 <xsd:complexType name="ShipmentVolume_V1" xdb:SQLType="SHIPMENT_VOLUME_T">
 <xsd:annotation>
 <xsd:documentation>A measurement for shipment volume</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="Unit" type="xsd:string" minOccurs="0" xdb:SQLName="UNIT"/>
 <xsd:element name="Value" type="xsd:decimal" minOccurs="0" xdb:SQLName="VALUE"/>
 </xsd:sequence>
 </xsd:complexType>
 
</xsd:schema>
CorridorRate.xsd
<?xml version="1.0" encoding="utf-8"?>

<xsd:schema xmlns="http://com.oocl.schema.tnm.agreementbuilder" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:tnm="http://com.oocl.schema.tnm" xmlns:common="http://com.oocl.schema.common" xmlns:fwd="http://com.oocl.frm.common.date.dto/" xmlns:customer="http://com.oocl.schema.customer" xmlns:eqm="http://com.oocl.schema.eqm" targetNamespace="http://com.oocl.schema.tnm.agreementbuilder" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
 <xsd:include schemaLocation="AB_Common_V1_XMLDB.xsd"/>
 <xsd:element name="CorridorRate" type="CorridorRate_V1" nillable="true" xdb:SQLName="CORRIDOR_RATE"/>
 
 <xsd:simpleType name="DeliveryMode_V1">
 <xsd:annotation>
 <xsd:documentation>2 char string representing the delivery mode associated with the rate. YY for example is a Container Yard to Container Yard move, whereas DD is a door to door move.</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="2"/>
 <xsd:minLength value="2"/>
 <xsd:enumeration value="YY"/>
 <xsd:enumeration value="YD"/>
 <xsd:enumeration value="DY"/>
 <xsd:enumeration value="DD"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:simpleType name="PaymentTerm_V1">
 <xsd:annotation>
 <xsd:documentation>Payment term, either prepaid or collect</xsd:documentation>
 </xsd:annotation>
 <xsd:restriction base="xsd:string">
 <xsd:maxLength value="10"/>
 <xsd:enumeration value="Prepaid"/>
 <xsd:enumeration value="Collect"/>
 </xsd:restriction>
 </xsd:simpleType>
 
 <xsd:complexType name="CorridorMetric_V1" xdb:SQLType="CORRIDOR_METRIC_T">
 <xsd:annotation>
 <xsd:documentation>Corridor metrics associated with corridor base rate</xsd:documentation>
 </xsd:annotation>
 <xsd:sequence>
 <xsd:element name="SizeType" type="xsd:string" minOccurs="0" xdb:SQLName="SIZE_TYPE">
 <xsd:annotation>
 <xsd:documentation>container sise and type that the rate is applicable</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="VolumeSRG" type="xsd:string" minOccurs="0" xdb:SQLName="VOLUME_SRG">
 <xsd:annotation>
 <xsd:documentation>guideline volume</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="AgreementSRG" type="xsd:string" minOccurs="0" xdb:SQLName="AGREEMENT_SRG">
 <xsd:annotation>
 <xsd:documentation>ageeement volume</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="ContributionNRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_NRPO">
 <xsd:annotation>
 <xsd:documentation>contribution matrix NRPO</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="ContributionRPO" type="xsd:string" minOccurs="0" xdb:SQLName="CONTRIBUTION_RPO">
 <xsd:annotation>
 <xsd:documentation>contribution matrix RPO</xsd:documentation>
 </xsd:annotation>
 </xsd:element>
 <xsd:element name="AverageRate" type="xsd:string" minOccurs="0" xdb:SQLName="AVERAGE_RATE">

Thanks so much for your response - Prefixing the call to the table within the package, with the schema owner does indeed solve the problem. Since this is a Production issue, i have implemented this fix in my customer's database.
However, I would still like this issue permanently resolved. The next time we send out updated package code, this will happen again (unless we then fix it again). I'd still like info from anyone on what exactly must be done to allow the call within the package to work without specifically pre-fixing the table's schema owner. It shouldn't be needed... The DB link is connecting via the same schema on database B that owns the table in question.
pre-fixing the schema owner is something we don't do in our sql statements, and this has worked fine for many of our cusomer's environments. We're only seeing this issue on one environment.

SIS Tables

Similar Messages

Maybe you are looking for