Integrator Data Loader and Data Extractor Field Definitions A-19 If the Local ID of a folder is the same as a Leaf ID, then the data will be loaded into the folder.
The Aggregate Stream Loader allows you disaggregate quantities that are at the aggregate context level; the Current Aggregate Stream extractor allows you to extract aggregates. The validation rules for this parser are described in “Integrator Validation Rules”.
Aggregate Stream Loader Rules
Rules to remember when using either the Aggregate Stream Loader or the Leaf Stream Loader:
■ While loading custom UOM data on leaf product LIN,LIN Type and GIN Type will be ignored.
■ Other GIn and Other UOM are case sensitive.
■ If there is any file group collision problem then the job will be aborted without parsing any data files.
■ <File name>.502.missing file carries both GIN and LIN even if any one is not found.
■ <File name>.503.missing file carries both local Global Id and Alternate Id even if any one is not found.
■ <File name>.504.missing file carries both Partner local Global Id and Alternate Id even if any one is not found.
■ If the local id of the folder is same as leaf id then the aggregate loader considers folder dimension for loading the data.
The Aggregate Stream Loader also allows you to aggregate on a time only basis taking data that are based on a weekly schedule and aggregating it into daily data. This allows you to collaborate with partners who forecast on a daily basis. This feature is available only if your forecasts are based on daily time periods. If you are loading a time-only aggregation data, and all contexts are at the leaf level, the time period context must be a weekly time period.
Although the table below depicts both Context and Period at aggregate levels, they are not required to be. Either Context, Period, or both can be at an aggregate level.
Different modes of aggregate loading are shown in the figures below.
If you assume that Context is at aggregate level and Period is at leaf level, as shown in the table below, it is as if the Period column.
Likewise, if the Period is at an aggregate level and Context is at a leaf level, is it as if the Context column did not exist. (seen below).
The columns you can define for the Aggregate Stream Loader are described in the Table below.
Table A–11 Aggregate Stream Loader Field Definitions
Column Description Value Optional
Creation Date The creation date of the stream. You cannot load a stream into the current stream table that has a creation date less than or equal to the prev_creation_date. For example, if you loaded a stream with a creation date of 10/30/2001, and the previous date is 10/29/2001, you cannot load a new stream with a date equal to or prior to 10/29/2001.
Also note that the creation date is translated into GMT in the database according to the time zone selected.
Format:
User Name The name of the user responsible. Up to 40 alphanumeric characters..
No
Creator Company ID
The Global Company ID of the company that created the data for the stream.
Up to 40 characters
Yes*
Creator Location ID
The location ID of the company, if it is leaf.
Local ID if it is folder.
Up to 40 characters
Yes*
Partner Company ID
Your trading partner’s company ID.
However, if the partner context contains a folder, this value must be the creator company ID if the creator company is local.
Up to 40
Your trading partner’s company Location ID, if it is leaf. Local ID if it is folder.
Period Begin The data stream’s beginning time period. YYYYMMDD No Period End The data stream’s ending time period. YYYYMMDD No
Quantity The data stream’s quantity. Numeric No
Aggregate Stream Loader
Integrator Data Loader and Data Extractor Field Definitions A-21
*Although marked “Yes” in the Optional column, these fields are conditionally optional, based on whether or not other information has been provided. For more details, see full explanation of “Conditionally Optional Fields”.
Data Stream Type Code
The type code you assigned to the data stream when you configured the control file for it.
Type Code No
Data Stream Item Type Code
The data stream item type code you assigned to the data stream item when you configured the control file for it.
Item Type Code No
Unit-of-Measure The UOM type. - Base UOM
- Custom UOM - Can be left blank for Base UOM.
Yes
Creator Company ID Type
The ID Type of the company that created the
data for the stream. Numeric;. Yes
Creator Company Alternate ID
The Alternate ID of the company that created the data for the stream.
Up to 40
The Alternate ID Type of the company that
created the data for the stream. Numeric Yes
Creator Location ID Type
The ID Type of the creator company’s
location. Numeric. Yes
Creator Location Alternate ID
The Alternate ID of the creator’s location. Up to 40 characters
Yes*
Creator Location Alternate ID Type
The Alternate ID Type of the creator location. Numeric Yes
Partner Compay ID Type
Your trading partner’s Company ID Type. Numeric Yes
Partner Company Alternate ID
Your trading partner’s Alternate Company ID.
Your trading partner’s Alternate Company
ID Type. Numeric Yes
Partner Location ID Type
Your trading partner’s Location ID Type. Numeric. Yes
Partner Location Alternate ID
Your trading partner’s Alternate Location ID. Up to 40 characters
Yes*
Partner Location Alternate ID Type
Your trading partner’s Alternate Location ID
Type. Numeric. Yes
Global Item Number Type
The product’s ID Type. Numeric. Yes
Local Item Number
The product’s Local Item Number. Up to 40 characters
Yes*
Local Item Number Type
The product’s Local Item Number Type. Numeric Yes Table A–11 (Cont.) Aggregate Stream Loader Field Definitions
Column Description Value Optional
If two disaggregation profiles have common collaboration items, when disaggregation is performed, creation date will be adjusted.
Before you can run the Aggregate Stream Loader, you must create an Aggregate Profile. This can be done using the Client. For details, see “About Aggregate Profiles”
in the VCC User Guide.
If you do not want to use an Aggregate Profile to load aggregate data, you must change the default settings in the Client to enable Straight-Line allocation. To do so, select “yes” in the Client’s Company - General Config - Preferences tab, as seen below.
This will apply the changes for the whole company.
When loading aggregate data, one dimension from the context must be at the
aggregate level. You must identify the dimension at the aggregate level by its folder ID (its local ID in the database).
The validation rules for the Aggregate Stream Loader are as follows:
If Creator Company is Local:
■ For the Creator Context
– If it is a folder, it must belong to the creator company – If it is a leaf, it must belong to the creator company
■ For the Partner Context
– If folder, it must belong to the creator company (if partner company is the same as creator, you can validate with partner company as well)
– If it is a leaf, it must belong to the partner company If Creator Company is not Local (company.isLocal = 0):
■ For the Creator Context
– If it is a folder, it must belong to the partner company – If it is a leaf, it must belong to the creator company
■ For the Partner Context
– If folder, it must belong to the partner company
Exception Loader/Extractor
Integrator Data Loader and Data Extractor Field Definitions A-23 – If it is a leaf, it must belong to the partner company
■ For the Product Context
– If it is a folder, it must belong to the partner company – If it is a leaf, it must belong to the partner company
Sample Aggregate Datafile
//If the creator company (111) is Local, then use the creator company DUNS number as the partner company DUNS number when the partner location is at the folder level