No | Business Term | Description |
1 | BAS BUSINESS SEGMENT | The BAS_Business_Segment [BasBusSg] and the BAS_Business_Segment_Hierarchy [BasBusSgHrchy] have been designed to tabularize the portions of an organizational chart that is reflected in the business transactions as structural units e.g. business unit, department, cost center and project).The fields within the BAS_Business_Segment [BasBusSg] are used to capture the individual organizational unit represented by each box on an organizational diagram. |
2 | BAS BUSINESS SEGMENT HIERARCHY | The fields in the BAS_Business_Segment_Hierarchy [BasBusSgHrchy] are used to capture the relationships between the individual organization units. The table assumes a one to one relationship and captures the data necessary to consolidate transactions occurring for child level organizational units into higher level organizational structures (for example, business unit to division). |
3 | BAS EMPLOYEE | Contains the personnel information of the employee in an independent accounting unit. |
4 | BAS USER | Contains the user information of accounting and/or ERP system. |
5 | BAS CUSTOMER TYPE | Contains detailed descriptions of the customer type. |
6 | BAS CUSTOMER | Contains essential and generic information of the customers. |
7 | BAS SUPPLIER TYPE | Contains detailed descriptions of the supplier type. |
8 | BAS SUPPLIER | Contains essential and generic information of the suppliers. |
9 | BAS CHART OF ACCOUNTS | Contains the information about GL accounts, including name, description, type and hierarchy. This table is level 1. When it is cross-referred by other table(s), consistency shall apply. For example, in this table, the value of GL_Account_Number [GlAcntNr] is 101, the value of GL_Account_Name [GlAcntNm] is cash, and the value of Balance_Debit_Or_Credit is D. If the value of GL_Account_Number [GlAcntNr] in GL_Tial_Balance table is 101, then the Amount corresponding with cash account (101) must be debit. |
10 | BAS ACCOUNTING PERIOD | Contains information related to the accounting period, including corresponding fiscal year, beginning date and ending date. The table captures the time range within a specific reporting period and year, in which business transactions and entries are accumulated into financial statements and other reports. |
11 | BAS JOURNAL ENTRY TYPE | Contains information relevant to the GL journal entry type (e.g. cash receipts, cash disbursements). |
12 | BAS BILL TYPE | The information of the bill type (e.g. bank draft, commercial draft, promissory note, check). Bills are frequently used in the business cycle of sales and purchase, as evidence of debt, payment and/or settlement instrument. |
13 | BAS SETTLEMENT METHOD | Contains information on methods used to settle transactions. Businesses can adopt various methods to settle transactions and transfer money, especially in sales and purchase activities. Typical settlement methods include cash settlements, issuing bills, using credit cards, bank remittances and bank collections. |
14 | BAS CURRENCY | Contains the information of the currency. |
15 | BAS MEASUREMENT UNIT | Contains information of the measurement unit (UOM) used in the modules of GL, SAL, PUR, INV and PPE. |
16 | BAS PAYMENT TERM | Contains the details of the payment term, which is applied and referenced in the PUR and SAL modules. The payment term refers to the condition of a sale/purchase agreement and is related to how the customer will pay (type of credit instrument), and especially how much time is allowed for payment (credit period) and discount (cash discount and discount period). |
17 | BAS PROJECT | Contains the detailed information related to the project (e.g. construction project, government or business-funded research project). Projects are commonly administrated separately and could be subject to being audit in accordance with regulatory and/or managerial requirements. The audit of a project is a thorough examination of the management, execution, methodology, procedures, records, budgets, expenditures, and the degree of completion. It is referenced in several modules including GL, AR, AP and INV. |
18 | BAS BANK ACCOUNT | Contains the details of a bank account. |
19 | BAS TAX REGULATORY | Contains regulatory information related to taxes, including regulator country, region, name and role. |
20 | BAS TAX TYPE | Contains detailed information on tax types used by the business. The tables in AR, SAL, AP and PUR modules contain 4 tax types, which can meet the requirements in most cases of the business. Tax types could be tax in country level, state level, county level or in local level, or could be tax related to a transaction (e.g. sales tax, value added tax, tariff). |
21 | BAS CUSTOMIZED ACC SEGMENT | An Account Segment is a customized file item, which includes the information of the customized account segments that are not fixed account segments and no other table contains their description information (e.g. region type). This table is used together with the BAS_Customized_ACC_Value [BasCstmzdAccValue]. |
22 | BAS CUSTOMIZED ACC VALUE | Contains the information from the customized account segment value. |
23 | BAS PROFILE | Contains industry and software version information. This table contains information related to the profile of the data being collected. For example, when we extract the financial data of 2016 from an auditee using SAP XXX ERP System in 2017.1.16, there should be a record with the Profile_Name [ProfileNm] "XXX_2016", Fiscal_Year [FiscYr] "2016", Developer_Name [DvlprNm] "SAP", Software_Name [SftwNm] "SAP_S/4", Software_Version [SftwVers] "2.0", Functional_Currency "CNY", Standard_Version [StdVers] "ISO 21378", Extracted_Date [ExtractedDt] "2017-01-16". |
24 | GL TRIAL BALANCE | Contains all the ledger account balance information of the ADCS. The GL_Trial_Balance [GlTrialBal] file shall contain the ending balances at a point in time. The GL_Trial_Balance [GlTrialBal] should be extracted at the same time as the GL_Details [GlDtls] to prevent differences in transactions and balances. |
25 | GL DETAILS | Contains all of the journal entry details for each transaction (e.g. associated journal entry ID, associated account number, debits or credits associated with the journal entry line). This table should be at the journal entry line level. |
26 | GL SOURCE | Contains additional information about the sources provided in the GL_Details [GlDtls] table. Each source shall include a description of the ERP system or accounting package, from which the data is extracted, and information related to the business process the data represents. |
27 | GL ACCOUNT SEGMENT | Contains the code and name for the account segment, as well as the GL_Account_Number [GlAcntNr] to which the account segment is related. Account Segment provides additional information for particular GL_Accounts (e.g. the AR contains the information regarding supplier, customer, employee, and project). Such information would be treated as an Account Segment below A/R, thus resulting in a lengthy account structure. The Account Segment structure is therefore defined as a set to record related information, which efficiently stops account names and numbers from becoming too long and too complex. Account Segment is more flexible to capture the complicated information.Some of the most frequently used account segments (e.g. project, employee, bank account) are defined as fixed fields in tables, such as GL_Details [GlDtls]. These segments are called "fixed account segments" in the document. Fixed account segments and other customized account segments are covered in this table. |
28 | GL ACCOUNT PERIOD BALANCE | Contains the cumulative total and balance of accounts in each accounting period, facilitating the calculation of beginning, ending balance, duration amounts and quantity, thus reflecting information and changes in GL more intuitively. In this table, the quantity can serve different regulatory and managerial purposes. For example, subledgers of inventory and PPE may not be covered in some auditees' systems. In this case, we can record the cumulative total and balance of quantity of inventory or PPE in this table. This is a well-established practice in some countries, like France and China. Countries can choose to use GL_Trial_Balance [GlTrialBal] or GL_Accounts_Period_Balance [GlAcntPerBal] or both, depending on their customary practice, regulatory and managerial requirements. |
29 | AR OPEN ACCOUNT RECEIVABLE | Contains details regarding all open, unpaid or unresolved customer transactions as of a specified date. Each row in this table represents the balance expected from the customer for one uniquely identifiable transaction. This data should be at the summary level (by invoice), not at the detailed level (by invoice line item). The sum total of the transaction amounts as of the specified date shall reconcile to the total AR amount in the GL as of the same date. |
30 | AR CASH RECEIVED | Contains information on all payment transactions received during the period. Cash means any type of receipt received including checks, wire transfers and cash. |
31 | AR CASH APPLICATION | Contains information of all cash receipts applied against the invoice during the period under review. The file will record each application of cash receipt to an invoice. For example, if a cash receipt was applied to three invoices, there will be three records for that receipt, one for each of the invoices to which the cash was applied. In the context of this process, cash means any type of receipt received including checks and wire transfers and cash. |
32 | AR ADJUSTMENT | Contains all adjustments recorded against the invoice and impacting the invoice balance during the period. (e.g. write-offs, credit memos, and other adjustments). The data set shall contain one record for each adjustment to each invoice. For example, if an adjustment transaction impacted three invoices, there shall be three records for that adjustment: one for each of the invoices impacted by the adjustment. |
33 | AR ADJUSTMENT DETAILS | Contains line item details for the invoices included in the AR_Adjustments [ArAdj]. |
34 | SAL CONTRACT | Contains summary information of sales contracts placed during the period under review. In situations where companies only require sales orders, the sales contract(s) may not always be available. |
35 | SAL CONTRACT DETAILS | Contains line item details for the sales contracts. Each line includes product, quantity, customer, price per unit and trading amount. |
36 | SAL ORDER | Contains summary information of sales orders pertinent to orders placed during the period under review. Sales orders are included in the three-way match procedures, which control the decision process for AR entries. |
37 | SAL ORDER DETAILS | Contains line item details for sales orders. Each line includes product, quantity, due date, price per unit, trading amount and settlement organization. Multiple types of products may be presented in one sales order. Additionally, different shippers and settlement organizations may be assigned by each order line. |
38 | SAL INVOICE GENERATED | Contains summary information for the invoices generated during the period under review. Invoices are included in the three-way match procedures, which control the decision process for AR entries. Each line includes invoice ID, invoice number, invoice date, customer, invoice amount, currency type, tax type, tax amount, settlement method and payment terms. |
39 | SAL INVOICE GENERATED DETAILS | Contains line item details for invoices. Each line includes invoice line information on specific products, measurement unit, price per unit, invoice amount, currency type, tax type code and tax amount. |
40 | SAL SHIPMENT MADE | Contains summary information for shipments and shipment adjustments made against sales orders during the period under review. Shipments made are included in the three-way match procedures, which control the decision process for AR entries. Each line includes shipment ID and Number, shipment date, shipping amount, customer information and currency type. |
41 | SAL SHIPMENT MADE DETAILS | Contains line item details for shipments and shipment adjustments. Each line includes shipments made, measurement unit, price per unit, order amount and currency type. |
42 | AP OPEN ACCOUNT PAYABLE | Contains details regarding all open, unpaid, or unresolved payable transactions as of a specified date. Each row in this table represents the balance due to the supplier for one uniquely identifiable transaction. This file should be at the summary level (by invoice), not at the detailed level (by invoice line item). The sum total of the transaction amounts as of the specified date shall reconcile to the total AP amount in the general ledger (GL) as of the same date. |
43 | AP PAYMENT MADE | Contains information on all payment transactions made during the period. Types of payments include check, wire transfer and cash. |
44 | AP CASH APPLICATION | Contains information of all cash payments applied against the invoice during the period under review. The table will have one line for each application of a cash payment to an invoice. For example, if a cash payment was applied to three invoices, there will be three records for that payment - one for each of the invoices to which the cash was applied. In the context of this process, cash means any type of payment received including checks and wire transfers and cash. |
45 | AP ADJUSTMENT | Contains all adjustments recorded against the invoice and impacting the invoice balance during the period. For example, write-offs, credit memos, and other adjustments. The table will have one line for each adjustment to each invoice. For example, if an adjustment transaction impacted three invoices, there will be three records for that adjustment-one for each of the invoices impacted by the adjustment. |
46 | AP ADJUSTMENT DETAILS | Contains line item details for the invoices included in the AP_Adjustments [ApAdj] table. The table will have one line for each invoice line item impacted by each adjustment. |
47 | PUR REQUISITION | Contains summary information for purchase requisitions placed during the period under review. |
48 | PUR REQUISITION DETAILS | Contains line item details for the purchase requisitions. The table contains material, quantity, due date, requisition organization and the purchase organization. |
49 | PUR CONTRACT | Contains summary information of a purchase contract placed during the period under review. In situations where companies only require purchase orders, the purchase contract(s) may not always be available. |
50 | PUR CONTRACT DETAILS | Contains line item details for the purchase contracts. Each line includes material, quantity, supplier, price per unit and trading amount. |
51 | PUR ORDER | Contains summary information of purchase orders placed during the period under review. Purchase orders are included in the three-way match procedures, which control the decision process for AP entries. |
52 | PUR ORDER DETAILS | Contains line item details for purchase orders. Each line includes material, quantity, due date, price per unit, trading amount, recipient and settlement organization. Multiple types of materials may be presented in one purchase order. |
53 | PUR INVOICE RECEIVED | Contains summary information for the invoices received during the period under review. Invoices are included in the three-way match procedures, which control the decision process for AP entries. Each line includes invoice ID, invoice number, invoice date, supplier, invoice amount, currency type, tax type, tax amount, settle method and payment terms. |
54 | PUR INVOICE RECEIVED DETAILS | Contains line item details for invoices. Each line includes invoice line information on specific materials, measurement unit, price per unit, invoice amount, currency type, tax type code, and tax amount. |
55 | PUR MATERIALS RECEIVED | Contains summary information for shipments and shipment adjustments received against purchase orders during the period under review. Materials received are included in the three-way match procedures, which control the decision process for AP entries. Each line includes receipt ID and Number, receipt date, receipt amount, supplier information and currency type. |
56 | PUR MATERIALS RECEIVED DETAILS | Contains line item details for shipments and shipment adjustment. Each line includes materials received, measurement unit, price per unit, order amount and currency type. |
57 | INV LOCATION | Contains information of an inventory location where inventory may be tracked. |
58 | INV PRODUCT TYPE | Contains inventory product type information and the tree structure information of inventory product type. |
59 | INV PRODUCT | Contains basic attributes of an inventory item and other tracked item through the purchase, use and sales. |
60 | INV ON HAND | Contains information of inventory on hand (e.g. suppliers, quantities of items by location and amounts as of the specified date). |
61 | INV TRANSACTION | Contains transaction history impacting the inventory accounts during the specified time period. |
62 | INV PHYSICAL INVENTORY | Contains the quantities on hand as of the date of the physical inventory count as well as the flow information. |
63 | INV PERIOD BALANCE | Contains inventory information regarding its beginning and ending balances, quantities and durational quantities and amounts. |
64 | PPE TYPE | Contains the details of each PPE type. |
65 | PPE MASTER | Contains the details of each PPE item (e.g. its code, specification, location, acquiring date, original cost, quantity). |
66 | PPE ADDITION | Contains the information of PPE addition transactions. |
67 | PPE REMOVAL | Contains the details related to PPE removal transactions. |
68 | PPE CHANGE | Contains changes in PPE information not related to additions and removals of PPE. Examples of information changes recorded include revaluation, historical cost, depreciation method and ownership. |
69 | PPE DEPARTMENT ALLOCATION | Contains information about how the related expenses are allocated among departments who benefit from using the PPE, especially the depreciation expenses. |
70 | PPE DEPRECIATION METHOD | Contains the information of depreciation methods used for PPE depreciation. |
71 | PPE DEPRECIATION | Contains the information correlating with PPE summarized depreciation in the period. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | BAS CUSTOMER | | -- | BasCust | | | | Contains essential and generic information of the customers. |
2 | A | 2 | Customer Account ID | IDENTIFIER 100 | 1..1 | CustAcntId | PK | | | Unique identifier for the customer. Typically auto-generated by the system. |
3 | A | 2 | Customer Account Number | IDENTIFIER 100 | 0..1 | CustAcntNr | | | | Number of the customer. This number is either generated by manual input or generated by the system. |
4 | A | 2 | Customer Account Name | NAME 200 | 0..1 | CustAcntNm | | | | Name of the customer. |
5 | A | 2 | Customer Abbreviation | NAME 100 | 0..1 | CustAbrv | | | | Abbreviation of the customer's name. |
6 | A | 2 | Parent Customer ID | IDENTIFIER 100 | 0..1 | ParCustId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the parent customer.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
7 | A | 2 | Corresponding Supplier ID | IDENTIFIER 100 | 0..1 | CorrSuplId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the corresponding supplier in cases where the customer is also a supplier.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. Otherwise, set NULL. |
8 | A | 2 | Customer Type ID | IDENTIFIER 60 | 0..1 | CustTypId | | BAS CUSTOMER TYPE | Customer Type ID | Unique identifier for the customer type.Typically auto-generated by the system.Shall match the Customer_Type_ID [CustTypId] in the BAS_Customer_Type [BasCustTyp] table. |
9 | A | 2 | Customer TIN | TAX IDENTIFICATION NUMBER | 0..1 | CustTin | | | | Customer's tax identification number.This number is usually generated by a tax regulator. |
10 | A | 2 | Inactive Date | DATE | 0..1 | InactiveDt | | | | Date when the customer was declared inactive.A customer can become inactive due to exceeding their credit limit, legal restrictions, contract termination or bankruptcy. |
11 | A | 2 | Transaction Credit Limit | AMOUNT | 0..1 | TrCrLimit | | | | Per invoice credit limit established for this customer. |
12 | A | 2 | Total Credit Limit | AMOUNT | 0..1 | TotCrLimit | | | | Credit limit for this customer’s total outstanding balance. |
13 | A | 2 | Terms Discount Percentage | PERCENTAGE | 0..1 | TrmsDscntPerc | | | | Discount percentage the customer can take if an invoice is paid before a certain number of days.In the flat file, terms are represented as integers to a decimal place.EXAMPLE 10 % is 0.10. |
14 | A | 2 | Terms Discount Days | NUMBER 6 | 0..1 | TrmsDscntDays | | | | Number of days from the invoice date that the customer has to take advantage of discounted terms.Terms are represented as integers with no decimal places.EXAMPLE 10 days are 10. |
15 | A | 2 | Terms Due Days | NUMBER 6 | 0..1 | TrmsDueDays | | | | Default number of days allowed to meet the obligation before an invoice becomes overdue. |
16 | E | 2 | PHYSICAL ADDRESS | | 0..1 | PhysAdr | | | | Physical address information. |
17 | A | 3 | Street Address1 | TEXT 100 | 0..1 | StreetAdr1 | | | | Line 1 of the street address. |
18 | A | 3 | Street Address2 | TEXT 100 | 0..1 | StreetAdr2 | | | | Line 2 of the street address. |
19 | A | 3 | City Name | CITY NAME | 0..1 | CityNm | | | | City name of this address. |
20 | A | 3 | State Province Code | STATE PROVINCE CODE | 0..1 | StatePrvncCd | | | | The state or province of this address (in accordance with ISO 3166-2). |
21 | A | 3 | Postal Code | POSTAL CODE | 0..1 | PostalCd | | | | Zip or postal code of this address. |
22 | A | 3 | Country Code | COUNTRY CODE | 0..1 | CntryCd | | | | The country code of this address (in accordance with ISO 3166-1). |
23 | E | 2 | BILLING ADDRESS | | 0..1 | BillAdr | | | | Billing address information. |
24 | A | 3 | Street Address1 | TEXT 100 | 0..1 | StreetAdr1 | | | | Line 1 of the street address. |
25 | A | 3 | Street Address2 | TEXT 100 | 0..1 | StreetAdr2 | | | | Line 2 of the street address. |
26 | A | 3 | City Name | CITY NAME | 0..1 | CityNm | | | | City name of this address. |
27 | A | 3 | State Province Code | STATE PROVINCE CODE | 0..1 | StatePrvncCd | | | | The state or province of this address (in accordance with ISO 3166-2). |
28 | A | 3 | Postal Code | POSTAL CODE | 0..1 | PostalCd | | | | Zip or postal code of this address. |
29 | A | 3 | Country Code | COUNTRY CODE | 0..1 | CntryCd | | | | The country code of this address (in accordance with ISO 3166-1). |
30 | E | 2 | PRIMARY CONTACT | | 0..1 | PrimCnt | | | | Primary contact information. |
31 | A | 3 | Name | NAME 100 | 0..1 | Nm | | | | Name of the contact. |
32 | A | 3 | Phone | PHONE NUMBER | 0..1 | Phone | | | | The phone number of the contact. |
33 | A | 3 | Email | EMAIL | 0..1 | Email | | | | The email address of the contact. |
34 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
35 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
36 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
37 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
38 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
39 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
40 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
41 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
42 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
43 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
44 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
45 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | BAS SUPPLIER | | -- | BasSupl | | | | Contains essential and generic information of the suppliers. |
2 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 1..1 | SuplAcntId | PK | | | Unique identifier for the supplier to whom payment is due or from whom unused credits have been applied.Typically auto-generated by the system. |
3 | A | 2 | Supplier Account Number | IDENTIFIER 100 | 0..1 | SuplAcntNr | | | | Number of the supplier to whom payment is due or from whom unused credits have been applied.This number is usually generated by manual input or is generated by the system. |
4 | A | 2 | Supplier Account Name | NAME 200 | 0..1 | SuplAcntNm | | | | Name of the supplier. |
5 | A | 2 | Supplier Abbreviation | NAME 100 | 0..1 | SuplAbrv | | | | Abbreviation form of the supplier's name. |
6 | A | 2 | Parent Supplier ID | IDENTIFIER 100 | 0..1 | ParSuplId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the parent supplier.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
7 | A | 2 | Corresponding Customer ID | IDENTIFIER 100 | 0..1 | CorrCustId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the corresponding customer in cases where the supplier is also a customer.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. Otherwise, set NULL. |
8 | A | 2 | Supplier Type ID | IDENTIFIER 60 | 0..1 | SuplTypId | | BAS SUPPLIER TYPE | Supplier Type ID | Unique identifier for the supplier type.Typically auto-generated by the system.Shall match the Supplier_Type_ID [SuplTypId] in the BAS_Supplier_Type [BasSuplTyp] table. |
9 | A | 2 | Supplier TIN | TAX IDENTIFICATION NUMBER | 0..1 | SuplTin | | | | Supplier's tax identification number.This number is usually generated by the tax regulator. |
10 | A | 2 | Supplier Group | TEXT 100 | 0..1 | SuplGroup | | | | Supplier group assignments when the organization segments the suppliers. |
11 | A | 2 | Inactive Date | DATE | 0..1 | InactiveDt | | | | Date when the supplier was declared inactive.A supplier can become inactive due to exceeding their credit limit, legal restrictions, contract termination or bankruptcy. |
12 | A | 2 | Transaction Credit Limit | AMOUNT | 0..1 | TrCrLimit | | | | Per invoice credit limit established for this supplier. |
13 | A | 2 | Total Credit Limit | AMOUNT | 0..1 | TotCrLimit | | | | Credit limit for the total outstanding balance approved for the supplier. |
14 | A | 2 | Terms Discount Percentage | PERCENTAGE | 0..1 | TrmsDscntPerc | | | | Discount percentage the supplier can provide if an invoice is paid before a certain number of days.In the flat file, terms are represented as integers to a decimal place.EXAMPLE 10 % is 0.10. |
15 | A | 2 | Terms Discount Days | NUMBER 6 | 0..1 | TrmsDscntDays | | | | Number of days from the invoice date that the supplier allows the customer to take advantage of discounted terms.Terms are represented as integers with no decimal places.EXAMPLE 10 days is 10. |
16 | A | 2 | Terms Due Days | NUMBER 6 | 0..1 | TrmsDueDays | | | | Number of days allowed to meet the obligation before an invoice becomes overdue. |
17 | E | 2 | PHYSICAL ADDRESS | | 0..1 | PhysAdr | | | | Physical address information. |
18 | A | 3 | Street Address1 | TEXT 100 | 0..1 | StreetAdr1 | | | | Line 1 of the street address. |
19 | A | 3 | Street Address2 | TEXT 100 | 0..1 | StreetAdr2 | | | | Line 2 of the street address. |
20 | A | 3 | City Name | CITY NAME | 0..1 | CityNm | | | | City name of this address. |
21 | A | 3 | State Province Code | STATE PROVINCE CODE | 0..1 | StatePrvncCd | | | | The state or province of this address (in accordance with ISO 3166-2). |
22 | A | 3 | Postal Code | POSTAL CODE | 0..1 | PostalCd | | | | Zip or postal code of this address. |
23 | A | 3 | Country Code | COUNTRY CODE | 0..1 | CntryCd | | | | The country code of this address (in accordance with ISO 3166-1). |
24 | E | 2 | BILLING ADDRESS | | 0..1 | BillAdr | | | | Billing address information. |
25 | A | 3 | Street Address1 | TEXT 100 | 0..1 | StreetAdr1 | | | | Line 1 of the street address. |
26 | A | 3 | Street Address2 | TEXT 100 | 0..1 | StreetAdr2 | | | | Line 2 of the street address. |
27 | A | 3 | City Name | CITY NAME | 0..1 | CityNm | | | | City name of this address. |
28 | A | 3 | State Province Code | STATE PROVINCE CODE | 0..1 | StatePrvncCd | | | | The state or province of this address (in accordance with ISO 3166-2). |
29 | A | 3 | Postal Code | POSTAL CODE | 0..1 | PostalCd | | | | Zip or postal code of this address. |
30 | A | 3 | Country Code | COUNTRY CODE | 0..1 | CntryCd | | | | The country code of this address (in accordance with ISO 3166-1). |
31 | E | 2 | PRIMARY CONTACT | | 0..1 | PrimCnt | | | | Primary contact information. |
32 | A | 3 | Name | NAME 100 | 0..1 | Nm | | | | Name of the contact. |
33 | A | 3 | Phone | PHONE NUMBER | 0..1 | Phone | | | | The phone number of the contact. |
34 | A | 3 | Email | EMAIL | 0..1 | Email | | | | The email address of the contact. |
35 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
36 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
37 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
38 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
39 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
40 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
41 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
42 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
43 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
44 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
45 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
46 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | GL DETAILS | | -- | GlDtls | | | | Contains all of the journal entry details for each transaction (e.g. associated journal entry ID, associated account number, debits or credits associated with the journal entry line). This table should be at the journal entry line level. |
2 | A | 2 | Journal ID | IDENTIFIER 100 | 1..1 | JrnId | PK | | | Unique identifier for each journal entry.Typically auto-generated by the system. |
3 | A | 2 | Journal Number | IDENTIFIER 100 | 0..1 | JrnNr | | | | Number of the journal entry (e.g. including serial number, document type, date). |
4 | A | 2 | GL Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account.Shall match the GL_Account_Number [GlAcntNr] used in the AS_Chart_Of_Accounts table. |
5 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Effective_Date [EffectiveDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Effective_Date [EffectiveDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date. Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
7 | A | 2 | Effective Date | DATE | 0..1 | EffectiveDt | | | | Date of the journal entry, no matter when the entry is received or created.This sometimes refers to the accounting date or accounting effective date.EXAMPLE If the user wants to see the financial results for the period ending March 5, 20XX, the journal entry may be created on any day during the open period and be assigned to the period ending March 5, 20XX. |
8 | A | 2 | Journal Line Number | TEXT 100 | 0..1 | JrnLnNr | | | | Number of the line within a journal entry.This number is generated either by manual input or by the system. |
9 | A | 2 | JE Type Code | IDENTIFIER 60 | 0..1 | JeTypCd | | BAS JOURNAL ENTRY TYPE | JE Type Code | Code for the journal entry type.Shall match the JE_Type_Code [JeTypCd] in the BAS_Journal_Entry_Type [BasJrnEntryTyp] table. |
10 | A | 2 | JE Header Description | TEXT 1000 | 0..1 | JeHdrDscr | | | | Description of the entire journal entry as described by the journal entry header. |
11 | A | 2 | JE Line Description | TEXT 1000 | 0..1 | JeLnDscr | | | | Description of the individual line within the journal entry. |
12 | A | 2 | Source Code | IDENTIFIER 25 | 0..1 | SrcCd | | GL SOURCE | Source Code | Code for the source from which the journal entry originated.EXAMPLE Sales journal, cash receipts journal, general journal, payroll journal, accountant manual entry, spreadsheet.Shall match the Source_Code [SrcCd] in the GL_Source [GlSrc] table. |
13 | A | 2 | Bill Number | TEXT 100 | 0..1 | BillNr | | | | Number of the bill.A bill usually includes bank drafts, promissory notes and checks. A bill may be issued by the drawer who agreed upon themselves or entrusts the drawee at sight. A specified date to the payee or bearer unconditionally pays a certain amount of securities.This number is generated either by manual input or by the system. |
14 | A | 2 | Bill Type Code | IDENTIFIER 60 | 0..1 | BillTypCd | | BAS BILL TYPE | Bill Type Code | Type of bill.EXAMPLE Bank drafts, promissory notes, checks.Shall match the Bill_Type_Code [BillTypCd] in the BAS_Bill_Type [BasBillTyp] table. |
15 | A | 2 | Bill Date | DATE | 0..1 | BillDt | | | | Date of the bill. |
16 | A | 2 | Quantity | QUANTITY | 0..1 | Qt | | | | Quantity of items referenced in the journal entry line.When the GL_Account_Number [GlAcntNr] is for inventories or fixed assets, this field is effective. If not, this field is NULL. |
17 | A | 2 | UOM Code | MEASUREMENT UNIT CODE | 0..1 | UomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the physical measurement scale for the inventory and PPE referred to as a "unit of measurement (UOM)".Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
18 | A | 2 | Unit Price | AMOUNT8 | 0..1 | UnitPrice | | | | Per unit price of the inventory or PPE.This field is associated with Quantity and Amount.EXAMPLE If the account is inventory or PPE, Quantity can be multiplied by Unit_Price [UnitPrice] to get total line Amount. |
19 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code value or indicator of the settlement method used for cash receipt from customers (i.e. sales) and cash payment to suppliers (i.e. purchase).EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
20 | A | 2 | Credit Debit Indicator | CREDIT DEBIT CODE | 0..1 | CrDbInd | | | | Indicates whether the amount is a credit or a debit.EXAMPLE C is credit, D is debit. |
21 | A | 2 | Reversal Indicator | REVERSAL INDICATOR CODE | 0..1 | RevInd | | | | Indicates whether this entry is a reversal or to be reversed.EXAMPLE 1 is the entry is a reversal, 2 is the entry is being reversed, an empty (" ") is none of the above or system-generated indicators. |
22 | A | 2 | Reversal Journal ID | IDENTIFIER 100 | 0..1 | RevJrnId | | | | When the Reversal_Indicator [RevInd] = 1, this field identifies the Journal_ID [JrnId] of the entry being reversed. |
23 | A | 2 | Cancellation Sign | BOOLEAN | 0..1 | CnclSign | | | | Sign of cancellation of a journal entry already formed but not yet posted.EXAMPLE 0 is entry is not cancelled, 1 is entry is cancelled. |
24 | A | 2 | Account Segment Employee | IDENTIFIER 60 | 0..1 | AcntSgEmp | | BAS EMPLOYEE | Employee ID | Fixed account segment, recording information related to an employee (e.g. loan to corporate officers).The value stored in this field stored is Employee_ID [EmpId].Shall match the Employee_ID [EmpId] in the BAS_Employee [BasEmp] table through GL_Account_Segment [GlAcntSg]. |
25 | A | 2 | Account Segment Project | IDENTIFIER 60 | 0..1 | AcntSgProj | | BAS PROJECT | Project ID | Fixed account segment, recording information related to a project.EXAMPLE Construction projects that require separate accounting.The value of this field stored is Project_ID [ProjId].Shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table through GL_Account_Segment [GlAcntSg]. |
26 | A | 2 | Account Segment Bank Account | IDENTIFIER 60 | 0..1 | AcntSgBankAcnt | | BAS BANK ACCOUNT | Bank Account Number | Fixed account segment, recording information related to bank accounts.The value of this field stored is Bank_Account_Number [BankAcntNr]. More information about a certain bank account can be obtained from the BAS_Bank_Account [BasBankAcnt] table.Shall match the Bank_Account_Number [BankAcntNr] in the BAS_Bank_Account [BasBankAcnt] table through GL_Account_Segment [GlAcntSg]. |
27 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
28 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
29 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
30 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
31 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
32 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
33 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
34 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
35 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
36 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
37 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
38 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
39 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
40 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
41 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
42 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
43 | E | 2 | POSTED | | 0..1 | Posted | | | | Information about the data that was posted. |
44 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
45 | E | 2 | ACCOUNT SEGMENT | | 0..n | AcntSg | | | | Contains associated Account Segment information. |
46 | A | 3 | Account Segment Number | TEXT 60 | 0..1 | AcntSgNr | | | | Sequence number of the associated Account Segment. Must match Account_Segment_Number [AcntSgNr] in GL_Account_Segment [GlAcntSg] in relation to the GL_Account_Number [GlAcntNr] concerned. |
47 | A | 3 | Account Segment Code | TEXT 60 | 0..1 | AcntSgCd | | | | Account Segment Code. |
48 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
49 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | GL ACCOUNT PERIOD BALANCE | | -- | GlAcntPerBal | | | | Contains the cumulative total and balance of accounts in each accounting period, facilitating the calculation of beginning, ending balance, duration amounts and quantity, thus reflecting information and changes in GL more intuitively. In this table, the quantity can serve different regulatory and managerial purposes. For example, subledgers of inventory and PPE may not be covered in some auditees' systems. In this case, we can record the cumulative total and balance of quantity of inventory or PPE in this table. This is a well-established practice in some countries, like France and China. Countries can choose to use GL_Trial_Balance [GlTrialBal] or GL_Accounts_Period_Balance [GlAcntPerBal] or both, depending on their customary practice, regulatory and managerial requirements. |
2 | A | 2 | GL Account Number | GL ACCOUNT NUMBER 100 | 1..1 | GlAcntNr | PK(1) | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] used in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
3 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 1..1 | FiscYr | PK(2) | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Effective_Date [EffectiveDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
4 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 1..1 | AcntingPer | PK(3)REFENT=BAS ACCOUNTING PERIOD | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the financial statement occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Debit Quantity | QUANTITY | 0..1 | DbQt | | | | Quantity information associated with the debiting inventory or PPE. |
6 | A | 2 | Credit Quantity | QUANTITY | 0..1 | CrQt | | | | Quantity information associated with the crediting inventory or PPE. |
7 | A | 2 | Beginning Quantity | QUANTITY | 0..1 | BegQt | | | | Beginning quantity of the inventory or PPE account. |
8 | A | 2 | Ending Quantity | QUANTITY | 0..1 | EndQt | | | | Ending quantity of the inventory or PPE account. |
9 | A | 2 | UOM Code | MEASUREMENT UNIT CODE | 0..1 | UomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the physical measurement scale for the inventory and PPE.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
10 | A | 2 | Beginning Balance Indicator | CREDIT DEBIT CODE | 0..1 | BegBalInd | | | | Beginning balance direction for the account, which indicates whether the beginning balance is debit or credit.EXAMPLE C is credit, D is debit. |
11 | A | 2 | Ending Balance Indicator | CREDIT DEBIT CODE | 0..1 | EndBalInd | | | | Ending balance direction for the account, which indicates whether the ending balance is debit or credit.EXAMPLE C is credit, D is debit. |
12 | A | 2 | Account Segment Employee | IDENTIFIER 60 | 0..1 | AcntSgEmp | | BAS EMPLOYEE | Employee ID | Fixed account segment, recording information related to an employee (e.g. loan to corporate officers).The value stored in this field stored is Employee_ID [EmpId].Shall match the Employee_ID [EmpId] in the BAS_Employee [BasEmp] table through GL_Account_Segment [GlAcntSg]. |
13 | A | 2 | Account Segment Project | IDENTIFIER 60 | 0..1 | AcntSgProj | | BAS PROJECT | Project ID | Fixed account segment, recording information related to a project.EXAMPLE Construction projects that require separate accounting.The value of this field stored is Project_ID [ProjId].Shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table through GL_Account_Segment [GlAcntSg]. |
14 | A | 2 | Account Segment Bank Account | IDENTIFIER 60 | 0..1 | AcntSgBankAcnt | | BAS BANK ACCOUNT | Bank Account Number | Fixed account segment, recording information related to bank accounts.The value of this field stored is Bank_Account_Number [BankAcntNr]. More information about a certain bank account can be obtained from the BAS_Bank_Account [BasBankAcnt] table.Shall match the Bank_Account_Number [BankAcntNr] in the BAS_Bank_Account [BasBankAcnt] table through GL_Account_Segment [GlAcntSg]. |
15 | E | 2 | DEBIT AMOUNT | | 0..1 | DbAmt | | | | The accumulative debit total during particular accounting period. |
16 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
17 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
18 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
19 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
20 | E | 2 | CREDIT AMOUNT | | 0..1 | CrAmt | | | | The accumulative credit total during particular accounting period. |
21 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
22 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
23 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
24 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
25 | E | 2 | BALANCE BEGINNING AMOUNT | | 0..1 | BalBegAmt | | | | The beginning balance amount. |
26 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
27 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
28 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
29 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
30 | E | 2 | BALANCE ENDING AMOUNT | | 0..1 | BalEndAmt | | | | The ending balance amount. |
31 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
32 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
33 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
34 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
35 | E | 2 | CURRENCY | | 0..1 | Cur | | | | Currency information. |
36 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
37 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
38 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
39 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
40 | E | 2 | ACCOUNT SEGMENT | | 0..n | AcntSg | | | | Contains associated Account Segment information. |
41 | A | 3 | Account Segment Number | TEXT 60 | 0..1 | AcntSgNr | | | | Sequence number of the associated Account Segment. Must match Account_Segment_Number [AcntSgNr] in GL_Account_Segment [GlAcntSg] in relation to the GL_Account_Number [GlAcntNr] concerned. |
42 | A | 3 | Account Segment Code | TEXT 60 | 0..1 | AcntSgCd | | | | Account Segment Code. |
43 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
44 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AR OPEN ACCOUNT RECEIVABLE | | -- | ArOpnAcntRcvbl | | | | Contains details regarding all open, unpaid or unresolved customer transactions as of a specified date. Each row in this table represents the balance expected from the customer for one uniquely identifiable transaction. This data should be at the summary level (by invoice), not at the detailed level (by invoice line item). The sum total of the transaction amounts as of the specified date shall reconcile to the total AR amount in the GL as of the same date. |
2 | A | 2 | Transaction ID | IDENTIFIER 60 | 1..1 | TrId | PK | | | Unique identifier for the transaction of an open AR that includes invoice and cash received.Typically auto-generated by the system. |
3 | A | 2 | Invoice ID | IDENTIFIER 60 | 0..1 | InvoiId | | SAL INVOICE GENERATED | Invoice ID | Unique identifier for the invoice, from which AR is derived.Typically auto-generated by the system.May be set to NULL if the adjustment is at the customer (not invoice) level. Otherwise shall match the Invoice_ID [InvoiId] in the SAL_Invoices_Generated [SalInvoiGen] table. |
4 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the customer from whom payment is expected or to whom unused credits have been applied.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
5 | A | 2 | Sales Contract ID | IDENTIFIER 60 | 0..1 | SalContrId | | SAL CONTRACT | Contract ID | Unique identifier for the sales contract from which AR is derived.Typically auto-generated by the system.May be set to NULL if there is no transaction related to Sales_Contract_ID [SalContrId]. Otherwise shall match the Sales_Contract_ID [SalContrId] in the SAL_Contracts [SalContr] table. |
6 | A | 2 | Project ID | IDENTIFIER 60 | 0..1 | ProjId | | | | Unique identifier for the project, from which AR is derived.Typically auto-generated by the system.May be set to NULL if no transaction is related to Project_ID [ProjId]. Otherwise shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table. |
7 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Transaction_Date [TrDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
8 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Transaction_Date [TrDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
9 | A | 2 | Transaction Date | DATE | 0..1 | TrDt | | | | Date of the transaction, regardless of the date when the transaction is created.This is the date from which the due date is calculated based on the invoice terms. |
10 | A | 2 | Journal ID | IDENTIFIER 100 | 0..1 | JrnId | | GL DETAILS | Journal ID | Unique identifier for journal entry.Typically auto-generated by the system.Shall match the Journal_ID [JrnId] in the GL_Details [GlDtls] table. |
11 | A | 2 | Transaction Due Date | DATE | 0..1 | TrDueDt | | | | Date when the payment is due from the customer.Not all transactions will have a due date. May be set to NULL if there is no due date (e.g. for credit memos). Aging of a receivable is usually calculated based on this date. |
12 | A | 2 | Reference Number | TEXT 100 | 0..1 | RefNr | | | | Number of an internally or externally generated transaction.EXAMPLE Check number, wire transfer number, original document ID. |
13 | A | 2 | Reference Date | DATE | 0..1 | RefDt | | | | Date on an internally or externally generated transaction.EXAMPLE Check date, wire transfer date. |
14 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
15 | A | 2 | Grouping Code | TEXT 100 | 0..1 | GrpCd | | | | Code for grouping related items for different purposes. |
16 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
17 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
18 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
19 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
20 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
22 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
23 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
24 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
25 | E | 2 | BALANCE AMOUNT | | 0..1 | BalAmt | | | | Balance monetary amounts recorded in their currency. The balance here refers to the remaining balance unpaid or needing settlement, which can be calculated by analyzing net of the originating invoice and any payment made and adjustments against it. |
26 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
27 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
28 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
29 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
30 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
31 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AR CASH RECEIVED | | -- | ArCashRcvd | | | | Contains information on all payment transactions received during the period. Cash means any type of receipt received including checks, wire transfers and cash. |
2 | A | 2 | Receipt ID | IDENTIFIER 60 | 1..1 | RcptId | PK | | | Unique identifier for the transaction of cash received.Typically auto-generated by the system. |
3 | A | 2 | Receipt Number | TEXT 100 | 0..1 | RcptNr | | | | Number of the cash received, from which AR is derived.This number is generated either by manual input or by the system. |
4 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the customer from whom payment is received or to whom credits have been applied.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
5 | A | 2 | Sales Contract ID | IDENTIFIER 60 | 0..1 | SalContrId | | SAL CONTRACT | Contract ID | Unique identifier for the sales contract from which AR is derived.Typically auto-generated by the system.May be set to NULL if there is no transaction related to Sales_Contract_ID [SalContrId].Otherwise shall match the Sales_Contract_ID [SalContrId] in the SAL_Contracts [SalContr] table. |
6 | A | 2 | Project ID | IDENTIFIER 60 | 0..1 | ProjId | | BAS PROJECT | Project ID | Unique identifier for the project, from which AR is derived.Typically auto-generated by the system.May be set to NULL if no transaction is related to Project_ID [ProjId]. Otherwise shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table. |
7 | A | 2 | Journal ID | IDENTIFIER 100 | 0..1 | JrnId | | GL DETAILS | Journal ID | Unique identifier for journal entry.Typically auto-generated by the system.Shall match the Journal_ID [JrnId] in the GL_Details [GlDtls] table. |
8 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Receipt_Date [RcptDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
9 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Receipt_Date [RcptDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
10 | A | 2 | Receipt Date | DATE | 0..1 | RcptDt | | | | Receipt date of the account receivable by the customer.EXAMPLE The received date of a check, wire transfer and cash. |
11 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code value or indicator for the method by which the transaction debit or credit amount was extinguished or apportioned to the debt by the customer.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
12 | A | 2 | Reference Number | TEXT 100 | 0..1 | RefNr | | | | Number of an internally or externally generated transaction.EXAMPLE Check number, wire transfer number, original document ID. |
13 | A | 2 | Reference Date | DATE | 0..1 | RefDt | | | | Date on an internally or externally generated transaction.EXAMPLE Check date, wire transfer date. |
14 | A | 2 | Amount Credit Debit Indicator | CREDIT DEBIT CODE | 0..1 | AmtCrDbInd | | | | Indicates whether the amount is a credit or a debit.EXAMPLE C is credit, D is debit. |
15 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
16 | A | 2 | GL Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
17 | A | 2 | GL Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
18 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
19 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
20 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
22 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
23 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
24 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
25 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
26 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
27 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
28 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
29 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
30 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
31 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
32 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
33 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
34 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
35 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
36 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
37 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
38 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
39 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
40 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AR CASH APPLICATION | | -- | ArCashApl | | | | Contains information of all cash receipts applied against the invoice during the period under review. The file will record each application of cash receipt to an invoice. For example, if a cash receipt was applied to three invoices, there will be three records for that receipt, one for each of the invoices to which the cash was applied. In the context of this process, cash means any type of receipt received including checks and wire transfers and cash. |
2 | A | 2 | AR Application ID | IDENTIFIER 100 | 1..1 | ArAplId | PK | | | Unique identifier for the application of cash from a receipt to each invoice.Typically auto-generated by the system. |
3 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the AR_Application_Date [ArAplDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
4 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the AR_Application_Date [ArAplDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | AR Application Date | DATE | 0..1 | ArAplDt | | | | Date of the cash application transaction, regardless of the date when the transaction was created. |
6 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the customer from whom payment is expected or to whom unused credits have been applied.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
7 | A | 2 | Receipt ID | IDENTIFIER 60 | 0..1 | RcptId | | AR CASH RECEIVED | Receipt ID | Unique identifier for the transactional document, from which AR is derived.Typically auto-generated by the system.Shall match the Receipt_ID [RcptId] in the AR_Cash_Received [ArCashRcvd] table. |
8 | A | 2 | Invoice ID | IDENTIFIER 60 | 0..1 | InvoiId | | SAL INVOICE GENERATED | Invoice ID | Unique identifier for the invoice, from which AR is derived.Typically auto-generated by the system.May be set to NULL if the adjustment is at the customer (not invoice) level. Otherwise shall match the Invoice_ID [InvoiId] in the SAL_Invoices_Generated [SalInvoiGen] table. |
9 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code for the settlement method.Various methods can be used to settle transactions and transfer money.EXAMPLE Check, wire transfer, cash. Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
10 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
11 | A | 2 | GL Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
12 | A | 2 | GL Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
13 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
14 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
15 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
16 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
17 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
18 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
19 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
20 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
21 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
22 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
23 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
24 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
25 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
26 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
27 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
28 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
29 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
30 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
31 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
32 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
33 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
34 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
35 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AR ADJUSTMENT | | -- | ArAdj | | | | Contains all adjustments recorded against the invoice and impacting the invoice balance during the period. (e.g. write-offs, credit memos, and other adjustments). The data set shall contain one record for each adjustment to each invoice. For example, if an adjustment transaction impacted three invoices, there shall be three records for that adjustment: one for each of the invoices impacted by the adjustment. |
2 | A | 2 | Adjustment ID | IDENTIFIER 100 | 1..1 | AdjId | PK | | | Unique identifier for the adjustment of a record.Typically auto-generated by the system. |
3 | A | 2 | Adjustment Number | TEXT 100 | 0..1 | AdjNr | | | | Number of the adjustment of the record.This number is generated either by manual input or by the system. This number can be created by concatenating fields to uniquely identify each transaction (e.g. serial number, document type, adjustment date). |
4 | A | 2 | Adjustment Type Name | TEXT 60 | 0..1 | AdjTypNm | | | | Name of the method by which the transaction debit or credit amount was extinguished or apportioned to the debt by the customer.EXAMPLE Credit memo, debit memo, finance charge, other adjustments. |
5 | A | 2 | Adjustment Document Number | TEXT 100 | 0..1 | AdjDocNr | | | | Number of an internally generated adjustment document (e.g. credit memo).This number is usually generated by manual input or automated using system-based rules (e.g. document number, document type, year). |
6 | A | 2 | Invoice ID | IDENTIFIER 60 | 0..1 | InvoiId | | SAL INVOICE GENERATED | Invoice ID | Unique identifier for the invoice, from which AR is derived.Typically auto-generated by the system.This field represents the invoice against which the adjustment is applied, if relevant.May be set to NULL if the adjustment is at the customer (not invoice) level. Otherwise shall match the Invoice_ID [InvoiId] in the SAL_Invoices_Generated [SalInvoiGen] table. |
7 | A | 2 | Journal ID | IDENTIFIER 100 | 0..1 | JrnId | | GL DETAILS | Journal ID | Unique identifier for journal entry.Typically auto-generated by the system.Shall match the Journal_ID [JrnId] in the GL_Details [GlDtls] table. |
8 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Adjustment_Date [AdjDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
9 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Adjustment_Date [AdjDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
10 | A | 2 | Adjustment Date | DATE | 0..1 | AdjDt | | | | Date of the adjustment, regardless of the date when the adjustment was created. |
11 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the customer from whom payment is expected or to whom unused credits have been applied.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
12 | A | 2 | GL Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
13 | A | 2 | GL Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
14 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
15 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
16 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
17 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
18 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
19 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
20 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
22 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
23 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
24 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
25 | A | 3 | Tax Local Amount | AMOUNT | 0..1 | TaxLocAmt | | | | The amount of Tax included in the transaction. Recorded in local currency. |
26 | A | 3 | GL Tax Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the debit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
27 | A | 3 | GL Tax Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the credit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
28 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
29 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
30 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
31 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
32 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
33 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
34 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
35 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
36 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
37 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
38 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
39 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
40 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
41 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | SAL ORDER | | -- | SalOrd | | | | Contains summary information of sales orders pertinent to orders placed during the period under review. Sales orders are included in the three-way match procedures, which control the decision process for AR entries. |
2 | A | 2 | Order ID | IDENTIFIER 100 | 1..1 | OrdId | PK | | | Unique identifier for the order.Typically auto-generated by the system. |
3 | A | 2 | Order Number | IDENTIFIER 100 | 0..1 | OrdNr | | | | Number of the order.This number is generated either by manual input or generated by the system. |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Order_Date [OrdDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Order_Date [OrdDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Order Type Name | TEXT 80 | 0..1 | OrdTypNm | | | | Name of the order type in sales or purchase activities.The types of sales orders are usually allocated by users of the system according to different business needs.EXAMPLE Some enterprises are configured as non-contract orders, trial orders, factory orders and store orders.EXAMPLE Ordinary purchasing, outsourcing parts, process outsourcing. |
7 | A | 2 | Order Date | DATE | 0..1 | OrdDt | | | | Date of the purchase order and date of signing of the sales order.It is the effective date of the order, not the system created date. The order of a certain period is counted based on the effective date. |
8 | A | 2 | Organization Code | IDENTIFIER 25 | 0..1 | OrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the sales of purchase organization that signed the order.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
9 | A | 2 | Salesperson ID | IDENTIFIER 60 | 0..1 | SalprsnId | | BAS EMPLOYEE | Employee ID | Unique identifier for the salesperson.Shall match the Employee_ID [EmpId] in the BAS_Employee [BasEmp] table. |
10 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the receiving customer.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
11 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code value or indicator for the method by which the transaction debit or credit amount was settled or apportioned by the customer or the supplier.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
12 | A | 2 | Payment Term Code | PAYMENT TERM CODE | 0..1 | PayTermCd | | BAS PAYMENT TERM | Payment Term Code | Code for the payment term.EXAMPLE Cash on delivery, payment 30 days after delivery date.Shall match the Payment_Term_Code [PayTermCd] in the BAS_Payment_Term [BasPayTerm] table. |
13 | A | 2 | Order Transaction Amount | AMOUNT | 0..1 | OrdTrAmt | | | | Transaction monetary amount recorded in transaction currency. |
14 | A | 2 | Order Transaction CUR Code | CURRENCY CODE | 0..1 | OrdTrCurCd | | | | Transactional currency specified in the order (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
15 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the order.EXAMPLE The order has been shipped (goods on the way), the order has been collected, the order has been completed.EXAMPLE New, save, submit, approved, frozen. |
16 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
17 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
18 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
19 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
20 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
21 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
22 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
23 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
24 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
25 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
26 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
27 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
28 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
29 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
30 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | SAL ORDER DETAILS | | -- | SalOrdDtls | | | | Contains line item details for sales orders. Each line includes product, quantity, due date, price per unit, trading amount and settlement organization. Multiple types of products may be presented in one sales order. Additionally, different shippers and settlement organizations may be assigned by each order line. |
2 | A | 2 | Order ID | IDENTIFIER 100 | 1..1 | OrdId | | SAL ORDER | Order ID | Unique identifier for the order.Typically auto-generated by the system.Shall match the Order_ID [OrdId] in the Order table. |
3 | A | 2 | Order Line ID | IDENTIFIER 60 | 1..1 | OrdLnId | PK | | | Unique identifier for a order line.Typically auto-generated by the system. |
4 | A | 2 | Order Line Number | TEXT 10 | 0..1 | OrdLnNr | | | | Number of the order line.This number is either generated by manual input or generated by the system. |
5 | A | 2 | Contract ID | IDENTIFIER 60 | 0..1 | ContrId | | SAL CONTRACT | | Unique identifier for the contract.Typically auto-generated by the system.May be set to NULL if there is no contract.Otherwise shall match the Contract_ID [ContrId] in the Contract_Details table. |
6 | A | 2 | Contract Line ID | IDENTIFIER 60 | 0..1 | ContrLnId | | SAL CONTRACT DETAILS | | The unique identifier for a contract line. Typically auto generated by the system. Shall match the Contract_Line_ID [ContrLnId] in the Contracts_Details table. |
7 | A | 2 | Payer ID | TEXT 60 | 0..1 | PayerId | | | | Unique identifier for the payer.Typically auto-generated by the system.There are different purchase models in the group company (e.g. centralized purchase, decentralized payment, decentralization of procurement, centralized payment). If the sales order customer adopts the centralized purchasing model, the customer may be a group company, and the settlement organization may be a subsidiary company of the group company. The customer name and the name of the payment customer may be different. |
8 | A | 2 | Settlement Organization Code | IDENTIFIER 25 | 0..1 | SetlOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the settlement organization.Both parties have settlement unit code, which is used to identify an organization for a sales order settlement.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
9 | A | 2 | Dispatch Organization Code | IDENTIFIER 25 | 0..1 | DispOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the dispatch organization.The dispatch unit refers to the unit who sends out goods belonging to the seller.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
10 | A | 2 | Due Date | DATE | 0..1 | DueDt | | | | Last requested delivery of products. When an order is delivered in multiple batches, this field refers to the time for the delivery of the last batch. |
11 | A | 2 | Basic UOM Quantity | QUANTITY | 0..1 | BasicUomQt | | | | Quantity by basic measurement unit. |
12 | A | 2 | Basic UOM Code | MEASUREMENT UNIT CODE | 0..1 | BasicUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the basic measurement unit in the order, which cannot be further seperated. Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
13 | A | 2 | Order Line Quantity | QUANTITY | 0..1 | OrdLnQt | | | | Quantity of the order line by the measurement unit in the order line. |
14 | A | 2 | Order Line UOM Code | MEASUREMENT UNIT CODE | 0..1 | OrdLnUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit in the order line.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
15 | A | 2 | Tax Exclude Unit Price | PRICE | 0..1 | TaxExclUnitPrice | | | | Unit price (excluding tax) in the transaction currency. |
16 | A | 2 | Tax Include Unit Price | PRICE | 0..1 | TaxInclUnitPrice | | | | Unit price (including tax) in the transaction currency. |
17 | A | 2 | Tax Exclude Amount | AMOUNT | 0..1 | TaxExclAmt | | | | Amount (excluding tax) in the transaction currency. |
18 | A | 2 | Tax Include Amount | AMOUNT | 0..1 | TaxInclAmt | | | | Amount (including tax) in the transaction currency. |
19 | A | 2 | Product ID | IDENTIFIER 75 | 0..1 | PrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the product.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
20 | A | 2 | Order Line Transaction Amount | AMOUNT | 0..1 | OrdLnTrAmt | | | | Transaction currency amount of the order line. |
21 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the contract line.This describes changes in the execution of the contract line item. Different states will affect the execution and control of the business.EXAMPLE Termination, frozen, closed. |
22 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
23 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
24 | A | 3 | Tax Transaction Amount | AMOUNT | 0..1 | TaxTrAmt | | | | The amount of Tax included in the transaction. Recorded in transaction currency. |
25 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
26 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | SAL INVOICE GENERATED | | -- | SalInvoiGen | | | | Contains summary information for the invoices generated during the period under review. Invoices are included in the three-way match procedures, which control the decision process for AR entries. Each line includes invoice ID, invoice number, invoice date, customer, invoice amount, currency type, tax type, tax amount, settlement method and payment terms. |
2 | A | 2 | Invoice ID | IDENTIFIER 60 | 1..1 | InvoiId | PK | | | Unique identifier for the invoice.Typically auto-generated by the system.The same ID shall be used for all tables with invoice data. |
3 | A | 2 | Invoice Number | TEXT 100 | 0..1 | InvoiNr | | | | Number of the invoice.This number is usually generated by manual input or is system-generated (e.g. including serial number, document type, date). |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Invoice_Date [InvoiDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Invoice_Date [InvoiDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Official Invoice Code | TEXT 25 | 0..1 | OfficialInvoiCd | | | | Unique official code of the invoice, which is usually generated by the tax authorities. |
7 | A | 2 | Invoice Type Name | TEXT 60 | 0..1 | InvoiTypNm | | | | The name of the invoice type. The documents are classified according to business content. |
8 | A | 2 | Invoice Date | DATE | 0..1 | InvoiDt | | | | Date of the invoice, regardless of the date the invoice is created. This is the date from which the due date is calculated based on the invoice terms. |
9 | A | 2 | Invoice Due Date | DATE | 0..1 | InvoiDueDt | | | | Date when the payment is due.Aging of a receivable is usually calculated based on this date. |
10 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the receiving customer.Typically autogenerated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
11 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | | | Code value for the method used for cash receipts from customers.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
12 | A | 2 | Invoice Transaction Amount | AMOUNT | 0..1 | InvoiTrAmt | | | | The transaction monetary amount recorded in the functional or group currency.No multi-currency translation should be performed on this amount because all transactions are recorded in a single currency. |
13 | A | 2 | Invoice Transaction CUR Code | CURRENCY CODE | 0..1 | InvoiTrCurCd | | BAS CURRENCY | Currency Code | Transactional currency appearing in the invoice (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
14 | A | 2 | Payment Term Code | PAYMENT TERM CODE | 0..1 | PayTermCd | | BAS PAYMENT TERM | Payment Term Code | Code for the payment term.EXAMPLE Cash on delivery, payment 30 days after delivery date.Shall match the Payment_Term_Code [PayTermCd] in the BAS_Payment_Term [BasPayTerm] table. |
15 | A | 2 | Terms Discount Percentage | PERCENTAGE | 0..1 | TrmsDscntPerc | | | | Discount percentage that can be provided if an invoice is paid before a certain number of days.Terms are represented as integers to a decimal place.EXAMPLE 10 % is 0.10. |
16 | A | 2 | Terms Discount Days | NUMBER 6 | 0..1 | TrmsDscntDays | | | | Number of days from the invoice date that the customer has to take advantage of discounted terms.Terms are represented as integers with no decimal places.EXAMPLE 10 days are 10. |
17 | A | 2 | Terms Due Days | NUMBER 6 | 0..1 | TrmsDueDays | | | | Number of days allowed that the customer has to meet the obligation before an invoice becomes overdue. |
18 | A | 2 | Grouping Code | TEXT 100 | 0..1 | GrpCd | | | | Grouping mechanism for related items in a batch or grouping of invoices (e.g. the invoice grouping found in certain ERP systems). |
19 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the invoice.EXAMPLE New, save, submit, frozen. |
20 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
21 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
22 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
23 | A | 3 | Tax Transaction Amount | AMOUNT | 0..1 | TaxTrAmt | | | | The amount of Tax included in the transaction. Recorded in transaction currency. |
24 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
25 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
26 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
27 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
28 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
29 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
30 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
31 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
32 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
33 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
34 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
35 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
36 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
37 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | SAL INVOICE GENERATED DETAILS | | -- | SalInvoiGenDtls | | | | Contains line item details for invoices. Each line includes invoice line information on specific products, measurement unit, price per unit, invoice amount, currency type, tax type code and tax amount. |
2 | A | 2 | Invoice ID | IDENTIFIER 60 | 1..1 | InvoiId | | SAL INVOICE GENERATED | | Unique identifier for the invoice.Typically auto-generated by the system. The same ID shall be used for all tables with invoice data. Shall match the Invoice_ID [InvoiId] in the Invoices_Generated table. |
3 | A | 2 | Invoice Line ID | IDENTIFIER 60 | 1..1 | InvoiLnId | PK | | | The unique identifier for an invoice line.Typically auto-generated by the system. |
4 | A | 2 | Invoice Line Number | TEXT 10 | 0..1 | InvoiLnNr | | | | Number of an internally generated invoice line.This number is generated either by manual input or generated by the system. |
5 | A | 2 | Order ID | IDENTIFIER 100 | 0..1 | OrdId | | SAL ORDER | | The unique identifier for the order.Typically auto-generated by the system.May be set to NULL if there is no order.Otherwise shall match the Order_ID [OrdId] in the Orders table. |
6 | A | 2 | Order Line ID | IDENTIFIER 60 | 0..1 | OrdLnId | | SAL ORDER DETAILS | | Unique identifier for a order line.Typically autogenerated by the system.May be set to NULL if there is no order. Otherwise shall match the Order_Line_ID [OrdLnId] in the Orders_Details table. |
7 | A | 2 | Product ID | IDENTIFIER 75 | 0..1 | PrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the product.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
8 | A | 2 | Basic UOM Quantity | QUANTITY | 0..1 | BasicUomQt | | | | Quantity by basic measurement unit. |
9 | A | 2 | Basic UOM Code | MEASUREMENT UNIT CODE | 0..1 | BasicUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the basic measurement unit in the invoice, which cannot be further separated.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
10 | A | 2 | Invoice Quantity | QUANTITY | 0..1 | InvoiQt | | | | Quantity recorded in the invoice line by the measurement unit for product. |
11 | A | 2 | UOM Code | MEASUREMENT UNIT CODE | 0..1 | UomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit for the product.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
12 | A | 2 | Tax Exclude Unit Price | PRICE | 0..1 | TaxExclUnitPrice | | | | Unit price (excluding tax) in the transaction currency. |
13 | A | 2 | Tax Include Unit Price | PRICE | 0..1 | TaxInclUnitPrice | | | | Unit price (including tax) in the transaction currency. |
14 | A | 2 | Tax Exclude Amount | AMOUNT | 0..1 | TaxExclAmt | | | | Amount (excluding tax) in the transaction currency. |
15 | A | 2 | Tax Include Amount | AMOUNT | 0..1 | TaxInclAmt | | | | Amount (including tax) in the transaction currency. |
16 | A | 2 | Invoice Line Transaction Amount | AMOUNT | 0..1 | InvoiLnTrAmt | | | | Transaction monetary amount recorded in the transaction currency.No multi-currency translation should be performed on this amount because all transactions are recorded in a single currency. |
17 | A | 2 | Grouping Code | TEXT 100 | 0..1 | GrpCd | | | | Grouping mechanism for related items in a batch or grouping of invoices (e.g. the invoice grouping found in certain ERP systems). |
18 | A | 2 | GL Line Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlLnDbAcntNr | | | | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
19 | A | 2 | GL Line Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlLnCrAcntNr | | | | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
20 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
21 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
22 | A | 3 | Tax Transaction Amount | AMOUNT | 0..1 | TaxTrAmt | | | | The amount of Tax included in the transaction. Recorded in transaction currency. |
23 | A | 3 | GL Tax Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the debit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
24 | A | 3 | GL Tax Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the credit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
25 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
26 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | SAL SHIPMENT MADE | | -- | SalShpMade | | | | Contains summary information for shipments and shipment adjustments made against sales orders during the period under review. Shipments made are included in the three-way match procedures, which control the decision process for AR entries. Each line includes shipment ID and Number, shipment date, shipping amount, customer information and currency type. |
2 | A | 2 | Shipment ID | IDENTIFIER 100 | 1..1 | ShpId | PK | | | Unique identifier for the shipment.Typically auto-generated by the system. |
3 | A | 2 | Shipment Number | TEXT 100 | 0..1 | ShpNr | | | | Number of the shipment.This number is generated either by manual input or generated by the system. |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Shipment_Date [ShpDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Shipment_Date [ShpDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Dispatch Organization Code | IDENTIFIER 25 | 0..1 | DispOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the dispatch organization.The dispatch unit refers to the unit who send out goods belonging to the seller.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
7 | A | 2 | Shipment Date | DATE | 0..1 | ShpDt | | | | The date of the shipment (date shipped). |
8 | A | 2 | Shipment Reference Number | IDENTIFIER 100 | 0..1 | ShpRefNr | | | | Number of the reference shipping.The company reference or logistics company official waybill number. |
9 | A | 2 | Shipping Transaction Amount | AMOUNT | 0..1 | ShpngTrAmt | | | | Monetary amount for the items in the shipping document related to the sales order.Recorded in the transaction currency. |
10 | A | 2 | Shipping Transaction CUR Code | CURRENCY CODE | 0..1 | ShpngTrCurCd | | BAS CURRENCY | Currency Code | Transactional currency related to the shipping amount (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
11 | A | 2 | Shipment Method | TEXT 60 | 0..1 | ShpMthd | | | | Transportation used for shipping.EXAMPLE Air, train, truck, hand delivered. |
12 | A | 2 | Shipper | TEXT 25 | 0..1 | Shipper | | | | Organization or individual that is or who is responsible for shipping the goods.EXAMPLE UPS, Federal Express. |
13 | A | 2 | Adjustment Indicator | ADJUSTMENT INDICATOR | 0..1 | AdjInd | | | | Represented by 0 if the transaction is the original shipment transaction. Represented by 1 if the transaction is a shipment adjustment. |
14 | A | 2 | Adjustment Description | TEXT 1000 | 0..1 | AdjDscr | | | | If an adjustment was made to a shipment, a description should clarify the reason for the adjustment. |
15 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the receiving customer.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
16 | A | 2 | Sales Order ID | IDENTIFIER 100 | 0..1 | SalOrdId | | SAL ORDER | Order ID | Unique identifier for the sales order.Typically auto-generated by the system.When a shipment is made that includes goods from multiple orders. On the table SAL_Shipments_Made_Details, there will be a detailed relationship between the sales order details and the shipment made details. May be set to NULL if there is no sales order. Otherwise shall match the Sales_Order_ID [SalOrdId] in the SAL_Orders [SalOrd] table. |
17 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
18 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
19 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
20 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
21 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
22 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
23 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
24 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
25 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
26 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
27 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
28 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
29 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
30 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AP OPEN ACCOUNT PAYABLE | | -- | ApOpnAcntPbl | | | | Contains details regarding all open, unpaid, or unresolved payable transactions as of a specified date. Each row in this table represents the balance due to the supplier for one uniquely identifiable transaction. This file should be at the summary level (by invoice), not at the detailed level (by invoice line item). The sum total of the transaction amounts as of the specified date shall reconcile to the total AP amount in the general ledger (GL) as of the same date. |
2 | A | 2 | Transaction ID | IDENTIFIER 60 | 1..1 | TrId | PK | | | Unique identifier for the transaction of open AP that includes invoice and cash paid.Typically auto-generated by the system. |
3 | A | 2 | Invoice ID | IDENTIFIER 60 | 0..1 | InvoiId | | PUR INVOICE RECEIVED | Invoice ID | Unique identifier for the invoice, from which AP is derived.Typically auto-generated by the system.May be set to NULL if the adjustment is at the supplier (not invoice) level. Otherwise shall match the Invoice_ID [InvoiId] in the PUR_Invoices_Received [PurInvoiRcvd] table. |
4 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier to whom payment is expected or from whom unused credits have been applied.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
5 | A | 2 | Purchase Contract ID | IDENTIFIER 60 | 0..1 | PurContrId | | PUR CONTRACT | Contract ID | Unique identifier for the purchase contract, from which AP is derived.Typically auto-generated by the system.May be set to NULL if there is no Purchase_Contract_ID [PurContrId]. Otherwise shall match the Purchase_Contract_ID [PurContrId] in the PUR_Contracts [PurContr] table. |
6 | A | 2 | Project ID | IDENTIFIER 60 | 0..1 | ProjId | | BAS PROJECT | Project ID | Unique identifier for the project, from which AP is derived.Typically auto-generated by the system.May be set to NULL if no Project_ID [ProjId]. Otherwise shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table. |
7 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Transaction_Date [TrDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
8 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Transaction_Date [TrDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
9 | A | 2 | Transaction Date | DATE | 0..1 | TrDt | | | | Date of the transaction, regardless of the date when the transaction is created.This is the date from which the due date is calculated based on the invoice terms. |
10 | A | 2 | Journal ID | IDENTIFIER 100 | 0..1 | JrnId | | GL DETAILS | Journal ID | Unique identifier for journal entry.Typically auto-generated by the system.Shall match the Journal_ID [JrnId] in the GL_Details [GlDtls] table. |
11 | A | 2 | Transaction Due Date | DATE | 0..1 | TrDueDt | | | | Date when the payment is due from the supplier.Not all transactions will have a due date. May be set to NULL if there is no due date (e.g. for credit memos). Aging of a receivable is usually calculated based on this date. |
12 | A | 2 | Reference Number | TEXT 100 | 0..1 | RefNr | | | | Number of an internally or externally generated transaction.EXAMPLE Check number, wire transfer number, original document ID. |
13 | A | 2 | Reference Date | DATE | 0..1 | RefDt | | | | Date on an internally or externally generated transaction.EXAMPLE Check date, wire transfer date. |
14 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
15 | A | 2 | Grouping Code | TEXT 100 | 0..1 | GrpCd | | | | Code for grouping related items for different purposes. |
16 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
17 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
18 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
19 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
20 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
22 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
23 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
24 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
25 | E | 2 | BALANCE AMOUNT | | 0..1 | BalAmt | | | | Balance monetary amounts recorded in their currency. The balance here refers to the remaining balance unpaid or needing settlement, which can be calculated by analyzing net of the originating invoice and any payment made and adjustments against it. |
26 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
27 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
28 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
29 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
30 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
31 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AP PAYMENT MADE | | -- | ApPayMade | | | | Contains information on all payment transactions made during the period. Types of payments include check, wire transfer and cash. |
2 | A | 2 | Payment ID | IDENTIFIER 60 | 1..1 | PayId | PK | | | Unique identifier for each transaction of cash paid. Typically auto-generated by the system. |
3 | A | 2 | Payment Number | TEXT 100 | 0..1 | PayNr | | | | Number of the transactional document, from which AP is derived. This number is usually generated by manual input or automated using system-based rules. |
4 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier to whom payment is paid or from whom credits have been applied.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
5 | A | 2 | Purchase Contract ID | IDENTIFIER 60 | 0..1 | PurContrId | | PUR CONTRACT | Contract ID | Unique identifier for the purchase contract, from which AP is derived.Typically auto-generated by the system.May be set to NULL if no Purchase_Contract_ID [PurContrId]. Otherwise shall match the Purchase_Contract_ID [PurContrId] in the PUR_Contracts [PurContr] table. |
6 | A | 2 | Project ID | IDENTIFIER 60 | 0..1 | ProjId | | BAS PROJECT | Project ID | Unique identifier for the project, from which AP is derived.Typically auto-generated by the system.May be set to NULL if no Project_ID [ProjId]. Otherwise shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table. |
7 | A | 2 | Journal ID | IDENTIFIER 100 | 0..1 | JrnId | | GL DETAILS | Journal ID | Unique identifier for journal entry.Typically auto-generated by the system.Shall match the Journal_ID [JrnId] in the GL_Details [GlDtls] table. |
8 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Payment_Date [PayDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
9 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Payment_Date [PayDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
10 | A | 2 | Payment Date | DATE | 0..1 | PayDt | | | | Payment date of the account payable by the supplier. |
11 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code value or indicator for the method by which the transaction debit or credit amount was settled or apportioned by the supplier.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
12 | A | 2 | Reference Number | TEXT 100 | 0..1 | RefNr | | | | Number of an internally or externally generated transaction.EXAMPLE Check number, wire transfer number, original document ID. |
13 | A | 2 | Reference Date | DATE | 0..1 | RefDt | | | | Date on an internally or externally generated transaction.EXAMPLE Check date, wire transfer date. |
14 | A | 2 | Amount Credit Debit Indicator | CREDIT DEBIT CODE | 0..1 | AmtCrDbInd | | | | Indicates whether the amount is a credit or a debit.EXAMPLE C is credit, D is debit. |
15 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
16 | A | 2 | GL Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.This number is usually generated by manual input or automated using system-based rules.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
17 | A | 2 | GL Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.This number is usually generated by manual input or automated using system-based rules.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
18 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
19 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
20 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
22 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
23 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
24 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
25 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
26 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
27 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
28 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
29 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
30 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
31 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
32 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
33 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
34 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
35 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
36 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
37 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
38 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
39 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
40 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AP CASH APPLICATION | | -- | ApCashApl | | | | Contains information of all cash payments applied against the invoice during the period under review. The table will have one line for each application of a cash payment to an invoice. For example, if a cash payment was applied to three invoices, there will be three records for that payment - one for each of the invoices to which the cash was applied. In the context of this process, cash means any type of payment received including checks and wire transfers and cash. |
2 | A | 2 | AP Application ID | IDENTIFIER 100 | 1..1 | ApAplId | PK | | | Unique identifier for the application of cash from a payment to each invoice.Typically auto-generated by the system. |
3 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the AP_Application_Date [ApAplDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
4 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the AP_Application_Date [ApAplDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | AP Application Date | DATE | 0..1 | ApAplDt | | | | Date of the cash application transaction, regardless of the date when the transaction was created. |
6 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier to whom payment is due or from whom unused credits have been received.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
7 | A | 2 | Payment ID | IDENTIFIER 60 | 0..1 | PayId | | AP PAYMENT MADE | Payment ID | Unique identifier for the transactional document, from which AP is derived.Typically auto-generated by the system.Shall match the Payment_ID [PayId] in the AP_Payments_Made [ApPayMade] table. |
8 | A | 2 | Invoice ID | IDENTIFIER 60 | 0..1 | InvoiId | | PUR INVOICE RECEIVED | Invoice ID | Unique identifier for the invoice, from which AP is derived.Typically auto-generated by the system.May be set to NULL if the adjustment is at the supplier (not invoice) level. Otherwise shall match the Invoice_ID [InvoiId] in the PUR_Invoices_Received [PurInvoiRcvd] table. |
9 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code value or indicator for the method by which the transaction debit or credit amount was settled or apportioned by the supplier.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
10 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
11 | A | 2 | GL Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.This number is usually generated by manual input or automated using system-based rules.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
12 | A | 2 | GL Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.This number is usually generated by manual input or automated using system-based rules.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
13 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
14 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
15 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
16 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
17 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
18 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
19 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
20 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
21 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
22 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
23 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
24 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
25 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
26 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
27 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
28 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
29 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
30 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
31 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
32 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
33 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
34 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
35 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | AP ADJUSTMENT | | -- | ApAdj | | | | Contains all adjustments recorded against the invoice and impacting the invoice balance during the period. For example, write-offs, credit memos, and other adjustments. The table will have one line for each adjustment to each invoice. For example, if an adjustment transaction impacted three invoices, there will be three records for that adjustment-one for each of the invoices impacted by the adjustment. |
2 | A | 2 | Adjustment ID | IDENTIFIER 100 | 1..1 | AdjId | PK | | | Unique identifier for the adjustment of a record.Typically auto-generated by the system. |
3 | A | 2 | Adjustment Number | TEXT 100 | 0..1 | AdjNr | | | | Number of the adjustment of the record.This number is usually generated by manual input or automated using system based rules. This number may need to be created by concatenating fields to uniquely identify each transaction (e.g. serial number, document type, adjustment date). |
4 | A | 2 | Adjustment Type Name | TEXT 60 | 0..1 | AdjTypNm | | | | Name of the method by which the transaction debit or credit amount was extinguished or apportioned to the debt by the supplier.EXAMPLE Credit memo, debit memo, finance charge, other adjustments. |
5 | A | 2 | Adjustment Document Number | TEXT 100 | 0..1 | AdjDocNr | | | | Number of an internally generated adjustment document (e.g. credit memo).This number is usually generated by manual input or automated using system-based rules (e.g. document number, document type, year). |
6 | A | 2 | Invoice ID | IDENTIFIER 60 | 0..1 | InvoiId | | PUR INVOICE RECEIVED | Invoice ID | Unique identifier for the invoice, from which AP is derived.Typically auto-generated by the system.This field represents the invoice against which the adjustment is applied, if relevant. May be set to NULL if the adjustment is at the supplier (not invoice) level. Otherwise shall match the Invoice_ID [InvoiId] in the PUR_Invoices_Received [PurInvoiRcvd] table. |
7 | A | 2 | Journal ID | IDENTIFIER 100 | 0..1 | JrnId | | GL DETAILS | Journal ID | Unique identifier for journal entry.Typically auto-generated by the system.Shall match the Journal_ID [JrnId] in the GL_Details [GlDtls] table. |
8 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Adjustment_Date [AdjDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
9 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Adjustment_Date [AdjDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
10 | A | 2 | Adjustment Date | DATE | 0..1 | AdjDt | | | | Date of the adjustment, regardless of the date when the adjustment was created. |
11 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier from whom payment is expected or to whom unused credits have been applied.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
12 | A | 2 | GL Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
13 | A | 2 | GL Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
14 | E | 2 | TRANSACTION AMOUNT | | 0..1 | TrAmt | | | | Related amount expressed in functional, transaction, reporting and local currency. |
15 | A | 3 | Functional Amount | AMOUNT | 0..1 | FuncAmt | | | | Amount recorded in the functional or group currency. |
16 | A | 3 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Code of the functional or group currency (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
17 | A | 3 | Transaction Amount | AMOUNT | 0..1 | TrAmt | | | | Amount recorded in the transaction currency. |
18 | A | 3 | Transaction Currency Code | CURRENCY CODE | 0..1 | TrCurCd | | BAS CURRENCY | Currency Code | The code of currency used in the actual transaction (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
19 | A | 3 | Reporting Amount | AMOUNT | 0..1 | RprtAmt | | | | Amount recorded in the reporting currency. |
20 | A | 3 | Reporting Currency Code | CURRENCY CODE | 0..1 | RprtCurCd | | BAS CURRENCY | Currency Code | The code of currency used for non-consolidated reporting (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 3 | Local Amount | AMOUNT | 0..1 | LocAmt | | | | Amount recorded in the local currency. |
22 | A | 3 | Local Currency Code | CURRENCY CODE | 0..1 | LocCurCd | | BAS CURRENCY | Currency Code | The code of currency used for local country reporting requirements (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
23 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
24 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
25 | A | 3 | Tax Local Amount | AMOUNT | 0..1 | TaxLocAmt | | | | The amount of Tax included in the transaction. Recorded in local currency. |
26 | A | 3 | GL Tax Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the debit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
27 | A | 3 | GL Tax Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the credit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
28 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
29 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
30 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
31 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
32 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
33 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
34 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
35 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
36 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
37 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
38 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
39 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
40 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
41 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PUR ORDER | | -- | PurOrd | | | | Contains summary information of purchase orders placed during the period under review. Purchase orders are included in the three-way match procedures, which control the decision process for AP entries. |
2 | A | 2 | Order ID | IDENTIFIER 100 | 1..1 | OrdId | PK | | | Unique identifier for the order.Typically auto-generated by the system. |
3 | A | 2 | Order Number | IDENTIFIER 100 | 0..1 | OrdNr | | | | Number of the order.This number is generated either by manual input or generated by the system. |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Order_Date [OrdDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Order_Date [OrdDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Order Type Name | TEXT 80 | 0..1 | OrdTypNm | | | | Name of the order type in sales or purchase activities.The types of sales orders are usually allocated by users of the system according to different business needs.EXAMPLE Some enterprises are configured as non-contract orders, trial orders, factory orders and store orders.EXAMPLE Ordinary purchasing, outsourcing parts, process outsourcing. |
7 | A | 2 | Order Date | DATE | 0..1 | OrdDt | | | | Date of the purchase order and date of signing of the sales order.It is the effective date of the order, not the system created date. The order of a certain period is counted based on the effective date. |
8 | A | 2 | Organization Code | IDENTIFIER 25 | 0..1 | OrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the sales of purchase organization that signed the order.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
9 | A | 2 | Purchaser ID | IDENTIFIER 60 | 0..1 | PurrId | | BAS EMPLOYEE | Employee ID | Code of the person who was responsible for purchase orders.Shall match the Employee_ID [EmpId] in the BAS_Employee [BasEmp] table. |
10 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier account in the purchase order. Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
11 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | BAS SETTLEMENT METHOD | Settlement Method Code | Code value or indicator for the method by which the transaction debit or credit amount was settled or apportioned by the customer or the supplier.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
12 | A | 2 | Payment Term Code | PAYMENT TERM CODE | 0..1 | PayTermCd | | BAS PAYMENT TERM | Payment Term Code | Code for the payment term.EXAMPLE Cash on delivery, payment 30 days after delivery date.Shall match the Payment_Term_Code [PayTermCd] in the BAS_Payment_Term [BasPayTerm] table. |
13 | A | 2 | Order Transaction Amount | AMOUNT | 0..1 | OrdTrAmt | | | | Transaction monetary amount recorded in transaction currency. |
14 | A | 2 | Order Transaction CUR Code | CURRENCY CODE | 0..1 | OrdTrCurCd | | | | Transactional currency specified in the order (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
15 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the order.EXAMPLE The order has been shipped (goods on the way), the order has been collected, the order has been completed.EXAMPLE New, save, submit, approved, frozen. |
16 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
17 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
18 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
19 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
20 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
21 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
22 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
23 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
24 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
25 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
26 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
27 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
28 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
29 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
30 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PUR ORDER DETAILS | | -- | PurOrdDtls | | | | Contains line item details for purchase orders. Each line includes material, quantity, due date, price per unit, trading amount, recipient and settlement organization. Multiple types of materials may be presented in one purchase order. |
2 | A | 2 | Order ID | IDENTIFIER 100 | 1..1 | OrdId | | PUR ORDER | | Unique identifier for the order.Typically auto-generated by the system.Shall match the Order_ID [OrdId] in the Order table. |
3 | A | 2 | Order Line ID | IDENTIFIER 60 | 1..1 | OrdLnId | PK | | | Unique identifier for a order line.Typically auto-generated by the system. |
4 | A | 2 | Order Line Number | TEXT 10 | 0..1 | OrdLnNr | | | | Number of the order line.This number is either generated by manual input or generated by the system. |
5 | A | 2 | Contract ID | IDENTIFIER 60 | 0..1 | ContrId | | PUR CONTRACT | | Unique identifier for the contract.Typically auto-generated by the system.May be set to NULL if there is no contract.Otherwise shall match the Contract_ID [ContrId] in the Contract_Details table. |
6 | A | 2 | Contract Line ID | IDENTIFIER 60 | 0..1 | ContrLnId | | PUR CONTRACT DETAILS | | The unique identifier for a contract line. Typically auto generated by the system. Shall match the Contract_Line_ID [ContrLnId] in the Contracts_Details table. |
7 | A | 2 | Requisition ID | IDENTIFIER 60 | 0..1 | RqstnId | | PUR REQUISITION | Requisition ID | Unique identifier for the material purchase requisition.Typically autogenerated by the system.May be set to NULL if no transaction related purchase requisitions. Otherwise shall match the Requisition_ID [RqstnId] in the PUR_Requisitions [PurRqstn] table. |
8 | A | 2 | Requisition Line ID | IDENTIFIER 60 | 0..1 | RqstnLnId | | PUR REQUISITION DETAILS | Requisition Line ID | Unique identifier for a material purchase requisition line. A requisition form may apply for purchasing one or more materials. Each material requisitioned should be described in a seperate row.Typically auto-generated by the system.May be set to NULL if no transaction related purchase requisitions. Otherwise shall match the Requisition_Line_ID [RqstnLnId] in the PUR_Requisitions_Details [PurRqstnDtls] table. |
9 | A | 2 | Settlement Organization Code | IDENTIFIER 25 | 0..1 | SetlOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the settlement organization.Both parties have settlement unit code, which is used to identify an organization for a sales order settlement.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
10 | A | 2 | Receipt Organization Code | IDENTIFIER 25 | 0..1 | RcptOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the receiving materials organization (Receiving organization, can be different from the settlement organization). The organization receiving materials may be a warehouse or an administration organization.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
11 | A | 2 | Project ID | IDENTIFIER 60 | 0..1 | ProjId | | BAS PROJECT | Project ID | Unique identifier for the project.Typically auto-generated by the system. Shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table. |
12 | A | 2 | Due Date | DATE | 0..1 | DueDt | | | | Last requested delivery of products. When an order is delivered in multiple batches, this field refers to the time for the delivery of the last batch. |
13 | A | 2 | Basic UOM Quantity | QUANTITY | 0..1 | BasicUomQt | | | | Quantity by basic measurement unit. |
14 | A | 2 | Basic UOM Code | MEASUREMENT UNIT CODE | 0..1 | BasicUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the basic measurement unit in the order, which cannot be further seperated. Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
15 | A | 2 | Order Line Quantity | QUANTITY | 0..1 | OrdLnQt | | | | Quantity of the order line by the measurement unit in the order line. |
16 | A | 2 | Order Line UOM Code | MEASUREMENT UNIT CODE | 0..1 | OrdLnUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit in the order line.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
17 | A | 2 | Tax Exclude Unit Price | PRICE | 0..1 | TaxExclUnitPrice | | | | Unit price (excluding tax) in the transaction currency. |
18 | A | 2 | Tax Include Unit Price | PRICE | 0..1 | TaxInclUnitPrice | | | | Unit price (including tax) in the transaction currency. |
19 | A | 2 | Tax Exclude Amount | AMOUNT | 0..1 | TaxExclAmt | | | | Amount (excluding tax) in the transaction currency. |
20 | A | 2 | Tax Include Amount | AMOUNT | 0..1 | TaxInclAmt | | | | Amount (including tax) in the transaction currency. |
21 | A | 2 | Product ID | IDENTIFIER 75 | 0..1 | PrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the product.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
22 | A | 2 | Order Line Transaction Amount | AMOUNT | 0..1 | OrdLnTrAmt | | | | Transaction currency amount of the order line. |
23 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the contract line.This describes changes in the execution of the contract line item. Different states will affect the execution and control of the business.EXAMPLE Termination, frozen, closed. |
24 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
25 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
26 | A | 3 | Tax Transaction Amount | AMOUNT | 0..1 | TaxTrAmt | | | | The amount of Tax included in the transaction. Recorded in transaction currency. |
27 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
28 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PUR INVOICE RECEIVED | | -- | PurInvoiRcvd | | | | Contains summary information for the invoices received during the period under review. Invoices are included in the three-way match procedures, which control the decision process for AP entries. Each line includes invoice ID, invoice number, invoice date, supplier, invoice amount, currency type, tax type, tax amount, settle method and payment terms. |
2 | A | 2 | Invoice ID | IDENTIFIER 60 | 1..1 | InvoiId | PK | | | Unique identifier for the invoice.Typically auto-generated by the system.The same ID shall be used for all tables with invoice data. |
3 | A | 2 | Invoice Number | TEXT 100 | 0..1 | InvoiNr | | | | Number of the invoice.This number is usually generated by manual input or is system-generated (e.g. including serial number, document type, date). |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Invoice_Date [InvoiDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Invoice_Date [InvoiDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Official Invoice Code | TEXT 25 | 0..1 | OfficialInvoiCd | | | | Unique official code of the invoice, which is usually generated by the tax authorities. |
7 | A | 2 | Invoice Type Name | TEXT 60 | 0..1 | InvoiTypNm | | | | The name of the invoice type. The documents are classified according to business content. |
8 | A | 2 | Invoice Date | DATE | 0..1 | InvoiDt | | | | Date of the invoice, regardless of the date the invoice is created. This is the date from which the due date is calculated based on the invoice terms. |
9 | A | 2 | Invoice Due Date | DATE | 0..1 | InvoiDueDt | | | | Date when the payment is due.Aging of a receivable is usually calculated based on this date. |
10 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier to whom payment is due or from whom unused credits have been applied.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
11 | A | 2 | Settlement Organization Code | IDENTIFIER 25 | 0..1 | SetlOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | The unique code of the settlement organization (Organization of the payment, can be different from the receiving organization). May be the purchase organization or the receipt organization. Shall match the Unique_Bus_Seg_Code in the BAS_Business_Segment [BasBusSg] table. |
12 | A | 2 | Settlement Method Code | IDENTIFIER 60 | 0..1 | SetlMthdCd | | | | Code value for the method used for cash receipts from customers.EXAMPLE Check, wire transfer, cash.Shall match the Settlement_Method_Code [SetlMthdCd] in the BAS_Settlement_Method [BasSetlMthd] table. |
13 | A | 2 | Invoice Transaction Amount | AMOUNT | 0..1 | InvoiTrAmt | | | | The transaction monetary amount recorded in the functional or group currency.No multi-currency translation should be performed on this amount because all transactions are recorded in a single currency. |
14 | A | 2 | Invoice Transaction CUR Code | CURRENCY CODE | 0..1 | InvoiTrCurCd | | BAS CURRENCY | Currency Code | Transactional currency appearing in the invoice (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
15 | A | 2 | Payment Term Code | PAYMENT TERM CODE | 0..1 | PayTermCd | | BAS PAYMENT TERM | Payment Term Code | Code for the payment term.EXAMPLE Cash on delivery, payment 30 days after delivery date.Shall match the Payment_Term_Code [PayTermCd] in the BAS_Payment_Term [BasPayTerm] table. |
16 | A | 2 | Terms Discount Percentage | PERCENTAGE | 0..1 | TrmsDscntPerc | | | | Discount percentage that can be provided if an invoice is paid before a certain number of days.Terms are represented as integers to a decimal place.EXAMPLE 10 % is 0.10. |
17 | A | 2 | Terms Discount Days | NUMBER 6 | 0..1 | TrmsDscntDays | | | | Number of days from the invoice date that the customer has to take advantage of discounted terms.Terms are represented as integers with no decimal places.EXAMPLE 10 days are 10. |
18 | A | 2 | Terms Due Days | NUMBER 6 | 0..1 | TrmsDueDays | | | | Number of days allowed that the customer has to meet the obligation before an invoice becomes overdue. |
19 | A | 2 | Grouping Code | TEXT 100 | 0..1 | GrpCd | | | | Grouping mechanism for related items in a batch or grouping of invoices (e.g. the invoice grouping found in certain ERP systems). |
20 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the invoice.EXAMPLE New, save, submit, frozen. |
21 | A | 2 | Remark | TEXT 500 | 0..1 | Rmrk | | | | Free-form text description. |
22 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
23 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
24 | A | 3 | Tax Transaction Amount | AMOUNT | 0..1 | TaxTrAmt | | | | The amount of Tax included in the transaction. Recorded in transaction currency. |
25 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
26 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
27 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
28 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
29 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
30 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
31 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
32 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
33 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
34 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
35 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
36 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
37 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
38 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PUR INVOICE RECEIVED DETAILS | | -- | PurInvoiRcvdDtls | | | | Contains line item details for invoices. Each line includes invoice line information on specific materials, measurement unit, price per unit, invoice amount, currency type, tax type code, and tax amount. |
2 | A | 2 | Invoice ID | IDENTIFIER 60 | 1..1 | InvoiId | | PUR INVOICE RECEIVED | | Unique identifier for the invoice.Typically auto-generated by the system. The same ID shall be used for all tables with invoice data. Shall match the Invoice_ID [InvoiId] in the Invoices_Generated table. |
3 | A | 2 | Invoice Line ID | IDENTIFIER 60 | 1..1 | InvoiLnId | PK | | | The unique identifier for an invoice line.Typically auto-generated by the system. |
4 | A | 2 | Invoice Line Number | TEXT 10 | 0..1 | InvoiLnNr | | | | Number of an internally generated invoice line.This number is generated either by manual input or generated by the system. |
5 | A | 2 | Order ID | IDENTIFIER 100 | 0..1 | OrdId | | PUR ORDER | | The unique identifier for the order.Typically auto-generated by the system.May be set to NULL if there is no order.Otherwise shall match the Order_ID [OrdId] in the Orders table. |
6 | A | 2 | Order Line ID | IDENTIFIER 60 | 0..1 | OrdLnId | | | | Unique identifier for a order line.Typically autogenerated by the system.May be set to NULL if there is no order. Otherwise shall match the Order_Line_ID [OrdLnId] in the Orders_Details table. |
7 | A | 2 | Product ID | IDENTIFIER 75 | 0..1 | PrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the product.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
8 | A | 2 | Basic UOM Quantity | QUANTITY | 0..1 | BasicUomQt | | | | Quantity by basic measurement unit. |
9 | A | 2 | Basic UOM Code | MEASUREMENT UNIT CODE | 0..1 | BasicUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the basic measurement unit in the invoice, which cannot be further separated.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
10 | A | 2 | Invoice Quantity | QUANTITY | 0..1 | InvoiQt | | | | Quantity recorded in the invoice line by the measurement unit for product. |
11 | A | 2 | UOM Code | MEASUREMENT UNIT CODE | 0..1 | UomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit for the product.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
12 | A | 2 | Tax Exclude Unit Price | PRICE | 0..1 | TaxExclUnitPrice | | | | Unit price (excluding tax) in the transaction currency. |
13 | A | 2 | Tax Include Unit Price | PRICE | 0..1 | TaxInclUnitPrice | | | | Unit price (including tax) in the transaction currency. |
14 | A | 2 | Tax Exclude Amount | AMOUNT | 0..1 | TaxExclAmt | | | | Amount (excluding tax) in the transaction currency. |
15 | A | 2 | Tax Include Amount | AMOUNT | 0..1 | TaxInclAmt | | | | Amount (including tax) in the transaction currency. |
16 | A | 2 | Invoice Line Transaction Amount | AMOUNT | 0..1 | InvoiLnTrAmt | | | | Transaction monetary amount recorded in the transaction currency.No multi-currency translation should be performed on this amount because all transactions are recorded in a single currency. |
17 | A | 2 | Grouping Code | TEXT 100 | 0..1 | GrpCd | | | | Grouping mechanism for related items in a batch or grouping of invoices (e.g. the invoice grouping found in certain ERP systems). |
18 | A | 2 | GL Line Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlLnDbAcntNr | | | | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
19 | A | 2 | GL Line Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlLnCrAcntNr | | | | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
20 | E | 2 | TAX | | 0..4 | Tax | | | | Tax information. |
21 | A | 3 | Tax Type Code | TAX TYPE CODE | 0..1 | TaxTypCd | | BAS TAX TYPE | Tax Type Code | The code of Tax type. Shall match the Tax_Type_Code [TaxTypCd] in the BAS_Tax_Type [BasTaxTyp] table. |
22 | A | 3 | Tax Transaction Amount | AMOUNT | 0..1 | TaxTrAmt | | | | The amount of Tax included in the transaction. Recorded in transaction currency. |
23 | A | 3 | GL Tax Debit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxDbAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the debit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
24 | A | 3 | GL Tax Credit Account Number | GL ACCOUNT NUMBER 100 | 0..1 | GlTaxCrAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | The GL account number on which the credit side of the Tax transaction has been posted. Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
25 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
26 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PUR MATERIALS RECEIVED | | -- | PurMatRcvd | | | | Contains summary information for shipments and shipment adjustments received against purchase orders during the period under review. Materials received are included in the three-way match procedures, which control the decision process for AP entries. Each line includes receipt ID and Number, receipt date, receipt amount, supplier information and currency type. |
2 | A | 2 | Receipt ID | IDENTIFIER 100 | 1..1 | RcptId | PK | | | Unique identifier for the shipment receipt.Typically auto-generated by the system. |
3 | A | 2 | Receipt Number | TEXT 100 | 0..1 | RcptNr | | | | Number of the receipt.This number is generated either by manual input or by the system. |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Receipt_Date [RcptDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Receipt_Date [RcptDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Receipt Organization Code | IDENTIFIER 25 | 0..1 | RcptOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Unique code of the receiving materials organization (the receiving organization can be different from the settlement organization).The organization receiving materials may be a warehouse or an administration organization.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
7 | A | 2 | Receipt Date | DATE | 0..1 | RcptDt | | | | Date of the shipment receipt. |
8 | A | 2 | Receipt Reference Number | TEXT 100 | 0..1 | RcptRefNr | | | | Number of the reference of the receipt.The company reference or logistics company official waybill number. |
9 | A | 2 | Receipt Transaction Amount | AMOUNT | 0..1 | RcptTrAmt | | | | Monetary amount for the items in the receipt related to the purchase order in the transaction currency.This amount is calculated through the receipt details. |
10 | A | 2 | Receipt Transaction CUR Code | CURRENCY CODE | 0..1 | RcptTrCurCd | | BAS CURRENCY | Currency Code | Transactional currency appearing in the receipt (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
11 | A | 2 | Shipping Method | TEXT 60 | 0..1 | ShpngMthd | | | | Transportation used for shipping.EXAMPLE Air, train, truck, hand delivered. |
12 | A | 2 | Shipper | TEXT 25 | 0..1 | Shipper | | | | Organization or individual that is or who is responsible for shipping the goods.EXAMPLE UPS, Federal Express. |
13 | A | 2 | Adjustment Indicator | ADJUSTMENT INDICATOR | 0..1 | AdjInd | | | | Represented by 0 if the transaction is the original shipment transaction. Represented by 1 if the transaction is a shipment adjustment. |
14 | A | 2 | Adjustment Description | TEXT 1000 | 0..1 | AdjDscr | | | | If an adjustment was made to a receipt, a description should clarify the reason for the adjustment. |
15 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier to whom payment is due or from whom unused credits have been applied.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
16 | A | 2 | Purchase Order ID | IDENTIFIER 100 | 0..1 | PurOrdId | | PUR ORDER | Order ID | Unique identifier for the purchase order.Typically auto-generated by the system.May be set to NULL if there is no transaction-related purchase order. Otherwise shall match the Purchase_Order_ID [PurOrdId] in the PUR_Orders [PurOrd] table. |
17 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
18 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
19 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
20 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
21 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
22 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
23 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
24 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
25 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
26 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
27 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
28 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
29 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
30 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | INV ON HAND | | -- | InvOnHand | | | | Contains information of inventory on hand (e.g. suppliers, quantities of items by location and amounts as of the specified date). |
2 | A | 2 | Inventory ID | IDENTIFIER 75 | 1..1 | InvId | PK | | | Unique identifier for the inventory.Typically auto-generated by the system. The unique value means that each line in the data table under consideration has a unique, non-repetitive, serial number for identification. |
3 | A | 2 | Inventory Product ID | IDENTIFIER 75 | 0..1 | InvPrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the inventory item.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
4 | A | 2 | Lot Number | TEXT 60 | 0..1 | LotNr | | | | Number associated with a product that is used for tracking and managing the lot. |
5 | A | 2 | Serial Number | TEXT 60 | 0..1 | SerialNr | | | | Number associated with an individual product item that is used for tracking and managing.EXAMPLE A company purchases 10 computers, with each computer assigned an individual serial number. |
6 | A | 2 | Inventory ABC Code | INVENTORY ABC CODE | 0..1 | InvAbcCd | | | | Code for the importance, monetary value or other measure of the item according to Markov's rule for selective inventory control, where 20 % of items are responsible for 80 % of the value or risk.A = top 20 % representing 80 % of risk:B = 30 %, representing 15 % of risk:C = 50 % of items representing only 5 % of risk. |
7 | A | 2 | Location ID | IDENTIFIER 75 | 0..1 | LctId | | INV LOCATION | Location ID | Unique identifier for the organization.Shall be a valid entry in the INV_Location [InvLct] table.Typically auto-generated by the system.Shall match the Location_ID [LctId] in the INV_Location [InvLct] table. |
8 | A | 2 | Inventory As Of Date | DATE | 0..1 | InvAsOfDt | | | | Specified date to which inventory information applies. |
9 | A | 2 | INV PUR YearToDate Quantity | QUANTITY | 0..1 | InvPurYrtodtQt | | | | Quantity purchased to this location year to date in the Basic_UOM_Code [BasicUomCd]. |
10 | A | 2 | INV Sold YearToDate Quantity | QUANTITY | 0..1 | InvSoldYrtodtQt | | | | Quantity sold from this location year to date in the Basic_UOM_Code [BasicUomCd]. |
11 | A | 2 | Inventory Organization Code | IDENTIFIER 25 | 0..1 | InvOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Code for the inventory organization, which refers to the organizational unit, physical or virtual, where the inventory transaction and balances may be tracked and monitored.It provides inventory information to modules such as purchase and sales. The simplest form of inventory organization is warehouse.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
12 | A | 2 | Cost Organization Code | IDENTIFIER 25 | 0..1 | CostOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Code for the cost organization, which refers to the organizational unit/level where the cost of outbound inventory will be calculated.The calculation may be done at the corporate level, the stocking organization level or at the particular locations where inventory is stored.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
13 | A | 2 | Inventory Costing UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvCstngUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit for the inventory's cost.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
14 | A | 2 | Inventory Purchasing UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvPrchsngUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the primary measurement unit of how goods enter the organization through purchase.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
15 | A | 2 | Inventory Selling UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvSellingUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the primary measurement unit of how goods leave the organization through sales.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
16 | A | 2 | Inventory Stocking UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvStckUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit used associated with the quantity used for stocking inventory.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
17 | A | 2 | Quantity | QUANTITY | 0..1 | Qt | | | | Book quantity as expressed in the Inventory_Stocking_UOM_Code [InvStckUomCd]. |
18 | A | 2 | System Quantity | QUANTITY | 0..1 | SystQt | | | | Actual quantity on hand from the physical count in the Basic_UOM_Code [BasicUomCd]. |
19 | A | 2 | Physical Count Quantity | QUANTITY | 0..1 | PhysCountQt | | | | Quantity on hand at the last physical count when multiple counts are performed in the Basic_UOM_Code [BasicUomCd]. |
20 | A | 2 | Last Count Date | DATE | 0..1 | LstCountDt | | | | Date of the last physical count. |
21 | A | 2 | Inventory List Price | AMOUNT | 0..1 | InvListPrice | | | | List or suggested retail price. |
22 | A | 2 | Inventory Cost | AMOUNT | 0..1 | InvCost | | | | Cost per unit using the method found in the Inventory_Cost_Method [InvCostMthd]. |
23 | A | 2 | Inventory Cost Method | TEXT 25 | 0..1 | InvCostMthd | | | | Description of the costing method.EXAMPLE LIFO, FIFO, average, standard, specific identification. |
24 | A | 2 | Average Cost | AMOUNT | 0..1 | AverageCost | | | | Average cost of per unit. |
25 | A | 2 | Standard Cost | AMOUNT | 0..1 | StdCost | | | | Standard cost per unit. |
26 | A | 2 | Specific Cost | AMOUNT | 0..1 | SpecificCost | | | | Specific cost per unit. |
27 | A | 2 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Functional or group currency related to the balance (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
28 | A | 2 | Bin ID | TEXT 25 | 0..1 | BinId | | | | Optional identifier for the sub-location. The code used in the system. |
29 | A | 2 | Bin Location | TEXT 50 | 0..1 | BinLct | | | | Description of the bin location used in the system. |
30 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
31 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | INV TRANSACTION | | -- | InvTr | | | | Contains transaction history impacting the inventory accounts during the specified time period. |
2 | A | 2 | Transaction Document ID | IDENTIFIER 100 | 1..1 | TrDocId | PK(1) | | | Unique identifier for the picking ticket, shipping notice or other document created upon or associated with movement.Typically auto-generated by the system. |
3 | A | 2 | Transaction Document Line ID | IDENTIFIER 100 | 1..1 | TrDocLnId | PK(2) | | | Unique identifier for the line number for a document other than a customer order or supplier purchase order.Typically auto-generated by the system. |
4 | A | 2 | Project ID | IDENTIFIER 60 | 0..1 | ProjId | | BAS PROJECT | Project ID | Unique identifier for the project.Typically auto-generated by the system.Shall match the Project_ID [ProjId] in the BAS_Project [BasProj] table. |
5 | A | 2 | Transaction Order ID | TEXT 100 | 0..1 | TrOrdId | | | | Unique identifier for the customer order, (supplier) purchase order or other document associated with the transaction.Typically auto-generated by the system. |
6 | A | 2 | Transaction Order Line ID | TEXT 100 | 0..1 | TrOrdLnId | | | | Unique identifier for the line item from a customer order or (supplier) purchase order, in order to differentiate between multiple items in a single order for different quantities.Typically auto-generated by the system. |
7 | A | 2 | Transaction Date | DATE | 0..1 | TrDt | | | | Date of activity per associated transaction document, if applicable. |
8 | A | 2 | Transaction Time | TIME | 0..1 | TrTm | | | | Time of the activity as per the associated transaction document, if applicable. |
9 | A | 2 | Transaction Type | TEXT 80 | 0..1 | TrTyp | | | | Captures information regarding movements and adjustments.Movement types may include receipt, shipment, transfer, return, moved to production and moved from production. Quantity adjustment types may include physical count adjustment, damage, obsolete and scrapped. Cost adjustments may include the lowering of cost or market realization. |
10 | A | 2 | Transaction Type System | TEXT 60 | 0..1 | TrTypSyst | | | | Transaction code local to the underlying accounting software system. |
11 | A | 2 | Transaction Description | TEXT 1000 | 0..1 | TrDscr | | | | Description of the transaction. |
12 | A | 2 | Transaction Quantity | QUANTITY | 0..1 | TrQt | | | | Quantity affected as expressed in the location stocking organization in the Basic_UOM_Code [BasicUomCd]. When the inventory is received, the number involved will be a positive number. When the inventory is dispatched, the number involved will be a negative number. |
13 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
14 | A | 2 | Customer Account ID | IDENTIFIER 100 | 0..1 | CustAcntId | | BAS CUSTOMER | Customer Account ID | Unique identifier for the receiving customer.Typically auto-generated by the system.Shall match the Customer_Account_ID [CustAcntId] in the BAS_Customer [BasCust] table. |
15 | A | 2 | Inventory Document ID | TEXT 60 | 0..1 | InvDocId | | | | Unique identifier for the inventory document, specifying the sources where the inventory originates.Typically auto-generated by the system. |
16 | A | 2 | Inventory Document Number | TEXT 80 | 0..1 | InvDocNr | | | | Number of the inventory document.This number is usually generated by manual input or is system-generated.EXAMPLE 201305020001. |
17 | A | 2 | Inventory Document Line ID | TEXT 60 | 0..1 | InvDocLnId | | | | Unique identifier for the inventory document line.Typically auto-generated by the system. |
18 | A | 2 | Inventory Document Line Number | TEXT 10 | 0..1 | InvDocLnNr | | | | Number of the inventory document line.This number is generated either by manual input or by the system. |
19 | A | 2 | Status | STATUS CODE | 0..1 | Stat | | | | Status of the inventory document.EXAMPLE New, save, submit, void, frozen. |
20 | A | 2 | Inventory Organization Code | IDENTIFIER 25 | 0..1 | InvOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Code for the inventory organization, which refers to the organizational unit, physical or virtual, where the inventory transaction and balances may be tracked and monitored.It provides inventory information to modules such as purchase and sales. The simplest form of inventory organization is warehouse.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
21 | A | 2 | Inventory Stocking UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvStckUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit used associated with the quantity used for stocking inventory.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
22 | A | 2 | Inventory Costing UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvCstngUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit for the inventory's cost.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
23 | A | 2 | Inventory Product ID | IDENTIFIER 75 | 0..1 | InvPrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the inventory item.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
24 | A | 2 | Lot Number | TEXT 60 | 0..1 | LotNr | | | | Number associated with a product that is used for tracking and managing the lot. |
25 | A | 2 | Serial Number | TEXT 60 | 0..1 | SerialNr | | | | Number associated with an individual product item that is used for tracking and managing.EXAMPLE A company purchases 10 computers, with each computer assigned an individual serial number. |
26 | A | 2 | Inventory Required By | TEXT 80 | 0..1 | InvRequiredBy | | | | Person or organization that makes the requisition for an inventory. |
27 | A | 2 | Inventory From Location ID | IDENTIFIER 75 | 0..1 | InvFromLctId | | INV LOCATION | Location ID | Unique identifier for the stock trading source location.Typically auto-generated by the system.Shall match the Location_ID [LctId] in the INV_Location [InvLct] table. |
28 | A | 2 | Inventory To Location ID | IDENTIFIER 75 | 0..1 | InvToLctId | | INV LOCATION | Location ID | Unique identifier for the stock trading destination.Typically auto-generated by the system.Shall match the Location_ID [LctId] in the INV_Location [InvLct] table. |
29 | A | 2 | Cost Organization Code | IDENTIFIER 25 | 0..1 | CostOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Code for the cost organization, which refers to the organizational unit/level where the cost of outbound inventory will be calculated.The calculation may be done at the corporate level, the stocking organization level or at the particular locations where inventory is stored.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
30 | A | 2 | Inventory Cost | AMOUNT | 0..1 | InvCost | | | | Cost per unit using the method found in the Inventory_Cost_Method [InvCostMthd]. |
31 | A | 2 | Transaction Adjustment Cost | AMOUNT | 0..1 | TrAdjCost | | | | Per unit increase or decrease in the stocking cost as represented in field Inventory_Cost_Method [InvCostMthd] of the INV_On_Hand [InvOnHand] table. |
32 | A | 2 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Functional or group currency related to the balance (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
33 | A | 2 | INV System Or External Source | SOURCE CODE | 0..1 | InvSystOrExtSrc | | | | Indicates whether the inventory transaction has originated within or outside the Inventory module.I is used for an internally initiated transaction and E is used for an externally initiated one.EXAMPLE Purchase or sale. |
34 | A | 2 | INV Received And Dispatched Code | INVENTORY RECEIVED DISPATCHED CODE | 0..1 | InvRcvdAndDispedCd | | | | Indicates whether the inventory is received or dispatched.EXAMPLE 0 is inventory received, 1 is inventory dispatched. |
35 | A | 2 | GL Line Debit Account ID | GL ACCOUNT NUMBER 100 | 0..1 | GlLnDbAcntId | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the debit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
36 | A | 2 | GL Line Credit Account ID | GL ACCOUNT NUMBER 100 | 0..1 | GlLnCrAcntId | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the credit side of the transaction has been posted.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
37 | E | 2 | POSTED | | 0..1 | Posted | | | | Information about the data that was posted. |
38 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
39 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
40 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
41 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
42 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
43 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
44 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
45 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
46 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
47 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
48 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
49 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
50 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
51 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
52 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
53 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
54 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | INV PHYSICAL INVENTORY | | -- | InvPhysInv | | | | Contains the quantities on hand as of the date of the physical inventory count as well as the flow information. |
2 | A | 2 | Inventory Count Sheet ID | IDENTIFIER 60 | 1..1 | InvCountShtId | PK(1) | | | Unique identifier for the inventory count sheet.Typically auto-generated by the system. |
3 | A | 2 | Inventory Count Sheet Number | TEXT 80 | 0..1 | InvCountShtNr | | | | Number of the inventory count sheet.This number is generated either by manual input or by the system. |
4 | A | 2 | Inventory Count Sheet Line ID | IDENTIFIER 60 | 1..1 | InvCountShtLnId | PK(2) | | | Unique identifier for the inventory count sheet line.Typically auto-generated by the system. |
5 | A | 2 | INV Count Sheet Line Number | TEXT 10 | 0..1 | InvCountShtLnNr | | | | Number of the line of the inventory count sheet.This number is generated either by manual input or by the system. |
6 | A | 2 | Inventory Product ID | IDENTIFIER 75 | 0..1 | InvPrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the inventory item.Typically auto-generated by the system.Shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct] table. |
7 | A | 2 | Location ID | IDENTIFIER 75 | 0..1 | LctId | | INV LOCATION | Location ID | Unique identifier for the organization.Shall be a valid entry in INV_Location [InvLct].Typically auto-generated by the system and used for data linking.Shall match the Location_ID [LctId] in the INV_Location [InvLct] table. |
8 | A | 2 | Inventory Organization Code | IDENTIFIER 25 | 0..1 | InvOrgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Code for the inventory organization.Shall match the Business_Segment_Code [BusSgCd] in the BAS_Business_Segment [BasBusSg] table. |
9 | A | 2 | Lot Number | TEXT 60 | 0..1 | LotNr | | | | Number associated with a product that is used for tracking and managing the lot. |
10 | A | 2 | Serial Number | TEXT 60 | 0..1 | SerialNr | | | | Number associated with an individual product item that is used for tracking and managing.EXAMPLE A company purchases 10 computers, with each computer assigned an individual serial number. |
11 | A | 2 | Bin ID | TEXT 25 | 0..1 | BinId | | | | Optional identifier for the sub-location. The code used in the system. |
12 | A | 2 | Count Date | DATE | 0..1 | CountDt | | | | Date of the physical count. |
13 | A | 2 | Inventory Stocking UOM Code | MEASUREMENT UNIT CODE | 0..1 | InvStckUomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit used associated with the quantity used for stocking inventory.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
14 | A | 2 | System Quantity | QUANTITY | 0..1 | SystQt | | | | Actual quantity on hand from the physical count in the Basic_UOM_Code [BasicUomCd]. |
15 | A | 2 | Phisical Count Quantity | QUANTITY | 0..1 | PhisicalCountQt | | | | Quantity on hand at the last physical count when multiple counts are performed in the Basic_UOM_Code [BasicUomCd]. |
16 | A | 2 | Comment | TEXT 200 | 0..1 | Comment | | | | Comments on the count, variances or other information captured. |
17 | E | 2 | POSTED | | 0..1 | Posted | | | | Information about the data that was posted. |
18 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
19 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
20 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
21 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
22 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
23 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
24 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
25 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
26 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
27 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
28 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
29 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
30 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
31 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
32 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
33 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
34 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PPE MASTER | | -- | PpeMaster | | | | Contains the details of each PPE item (e.g. its code, specification, location, acquiring date, original cost, quantity). |
2 | A | 2 | PPE ID | IDENTIFIER 100 | 1..1 | PpeId | PK | | | Unique identifier for the PPE.Typically auto-generated by the system. |
3 | A | 2 | PPE Code | TEXT 60 | 0..1 | PpeCd | | | | Internal code of the PPE at the local level. |
4 | A | 2 | Tag Number | TEXT 60 | 0..1 | TagNr | | | | Tag that used to be commonly used when there was no ERP system to record the PPE's state of the whole lifespan. It is still used by some ERP systems in the business of PPE.This number is usually generated by manual input or is system-generated.EXAMPLE When there is a PPE, a tag is created correspondingly. Each tag contains either one PPE or several PPEs. However, each PPE has its own PPE_ID [PpeId] as a unique identifier. If a tag only has one PPE, the PPE_ID [PpeId] is the same as the Tag_Number [TagNr]. |
5 | A | 2 | Type Code | IDENTIFIER 60 | 0..1 | TypCd | | PPE TYPE | Type Code | Unique code of the PPE type.Shall match the Type_Code [TypCd] in the PPE_Type [PpeTyp] table. |
6 | A | 2 | PPE Name | TEXT 60 | 0..1 | PpeNm | | | | Name of the PPE. |
7 | A | 2 | PPE Feature | TEXT 60 | 0..1 | PpeFeature | | | | Feature used to specify the PPE more clearly.EXAMPLE Brand, colour, size, configuration. |
8 | A | 2 | Bar Code | TEXT 25 | 0..1 | BarCd | | | | Universal Product Code or other external code.EXAMPLE The product code from a primary supplier. |
9 | A | 2 | Purchase Order ID | IDENTIFIER 100 | 0..1 | PurOrdId | | PUR ORDER | Order ID | Unique identifier for the purchase order.Typically auto-generated by the system.May be set to NULL if the PPE is not generated from a purchase order. Otherwise shall match the Purchase_Order_ID [PurOrdId] in the PUR_Orders_Details [PurOrdDtls] table. |
10 | A | 2 | Inventory Product ID | IDENTIFIER 75 | 0..1 | InvPrdctId | | INV PRODUCT | Inventory Product ID | Unique identifier for the inventory item.Typically auto-generated by the system.May be set to NULL if the PPE is not generated from inventory. Otherwise shall match the Inventory_Product_ID [InvPrdctId] in the INV_Product [InvPrdct]. |
11 | A | 2 | Serial Number | TEXT 60 | 0..1 | SerialNr | | | | Number associated with an individual PPE that is used for tracking and managing.EXAMPLE A company purchases 10 computers, with each computer assigned an individual serial number. |
12 | A | 2 | Lot Number | TEXT 60 | 0..1 | LotNr | | | | Number associated with a PPE that is used for tracking and managing the lot. |
13 | A | 2 | Manufacturer | TEXT 100 | 0..1 | Manufacturer | | | | Manufacturer of the PPE. |
14 | A | 2 | Supplier Account ID | IDENTIFIER 100 | 0..1 | SuplAcntId | | BAS SUPPLIER | Supplier Account ID | Unique identifier for the supplier.Typically auto-generated by the system.Shall match the Supplier_Account_ID [SuplAcntId] in the BAS_Supplier [BasSupl] table. |
15 | A | 2 | Location Description | TEXT 1000 | 0..1 | LctDscr | | | | Description of the location where the PPE is placed. |
16 | A | 2 | Condition Name | TEXT 60 | 0..1 | ConditionNm | | | | Name of the various usage status of PPE.EXAMPLE Asset in-use, not-in-use, not-in-use for seasonal reasons. |
17 | A | 2 | Acquisition Date | DATE | 0..1 | AcqDt | | | | Date when the PPE is acquired. |
18 | A | 2 | Posted Date | DATE | 0..1 | PostedDt | | | | Date when PPE is posted into accounts. |
19 | A | 2 | Placed Into Service Date | DATE | 0..1 | PlacedIntoSrvcDt | | | | Date that PPE is placed into use. |
20 | A | 2 | Quantity On Hand | QUANTITY | 0..1 | QtOnHand | | | | Quantity of PPE items on hand. |
21 | A | 2 | UOM Code | MEASUREMENT UNIT CODE | 0..1 | UomCd | | BAS MEASUREMENT UNIT | UOM Code | Code for the measurement unit for measuring the quantity of PPE.Shall match the UOM_Code [UomCd] in the BAS_Measurement_Unit [BasMeaUnit] table. |
22 | A | 2 | Useful Life | NUMBER 4 | 0..1 | UsefulLife | | | | Total useful life of the PPE in months. |
23 | A | 2 | Useful Life Remaining | NUMBER 4 | 0..1 | UsefulLifeRmng | | | | Remaining useful life of the PPE in months as of the report date. |
24 | A | 2 | Original Cost | AMOUNT | 0..1 | OriginalCost | | | | Original cost of the PPE. |
25 | A | 2 | Residual Value | AMOUNT | 0..1 | ResiValue | | | | Residual value of the PPE as of the report date.Typically calculated by an expected residual value ratio. |
26 | A | 2 | Accumulated Depreciation | AMOUNT | 0..1 | AccumDepre | | | | Accumulated depreciation of the PPE as of the report date. |
27 | A | 2 | Impairment Provision | AMOUNT | 0..1 | ImprProv | | | | Impairment provision of PPE as of the report date. |
28 | A | 2 | Net Book Value | AMOUNT | 0..1 | NetBookValue | | | | Net book value of PPE as of the report date, which equals the original cost minus accumulated depreciation and impairment provision. |
29 | A | 2 | Replacement Cost | AMOUNT | 0..1 | RplcCost | | | | Replacement cost of the PPE as of the report date. |
30 | A | 2 | Fair Value | AMOUNT | 0..1 | FairValue | | | | Fair value of PPE as of the report date. |
31 | A | 2 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | | | Functional or group currency related to the balance (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
32 | A | 2 | PPE Account Number | GL ACCOUNT NUMBER 100 | 0..1 | PpeAcntNr | | | | GL account number on which the Balance Sheet amount is recognized after the asset has been put into operation.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
33 | A | 2 | Impairment Provision ACC NUM | GL ACCOUNT NUMBER 100 | 0..1 | ImprProvAccNum | | | | Number of the GL account on which the Balance Sheet amount is recognized for an impairment provision account.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
34 | A | 2 | Accumulated Depreciation ACC NUM | GL ACCOUNT NUMBER 100 | 0..1 | AccumDepreAccNum | | | | Number of the GL account on which the Balance Sheet amount is recognized for accumulated depreciation.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
35 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
36 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
37 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
38 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
39 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
40 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
41 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
42 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
43 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
44 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
45 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
46 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
47 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
48 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PPE REMOVAL | | -- | PpeRmv | | | | Contains the details related to PPE removal transactions. |
2 | A | 2 | Removal ID | IDENTIFIER 60 | 1..1 | RmvId | PK | | | Unique identifier for the removal entry.Typically auto-generated by the system. |
3 | A | 2 | PPE ID | IDENTIFIER 100 | 0..1 | PpeId | | PPE MASTER | PPE ID | Unique identifier for the PPE.Typically auto-generated by the system.Shall match the PPE_ID [PpeId] in the PPE_Master [PpeMaster] table. |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Removal_Date [RmvDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Removal_Date [RmvDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Tag Number | TEXT 60 | 0..1 | TagNr | | | | Tag that used to be commonly used when there was no ERP system to record the PPE's state of the whole lifespan. It is still used by some ERP systems in the business of PPE.This number is usually generated by manual input or is system-generated.EXAMPLE When there is a PPE, a tag is created correspondingly. Each tag contains either one PPE or several PPEs. However, each PPE has its own PPE_ID [PpeId] as a unique identifier. If a tag only has one PPE, the PPE_ID [PpeId] is the same as the Tag_Number [TagNr]. |
7 | A | 2 | Removal Type Name | TEXT 60 | 0..1 | RmvTypNm | | | | Description of the removal type.EXAMPLE Sale, retirement, disposal, damaged. |
8 | A | 2 | Removal Date | DATE | 0..1 | RmvDt | | | | Date when the PPE is removed. |
9 | A | 2 | Removal Reason | TEXT 200 | 0..1 | RmvReason | | | | Reason why there was a removal. |
10 | A | 2 | Removal Quantity | QUANTITY | 0..1 | RmvQt | | | | Reduced quantity of the PPE. |
11 | A | 2 | Removal Original Cost | AMOUNT | 0..1 | RmvOriginalCost | | | | Reduced original cost during the removal transaction. |
12 | A | 2 | Removal Accumulated Depreciation | AMOUNT | 0..1 | RmvAccumDepre | | | | Reduced accumulated depreciation during the removal transaction. |
13 | A | 2 | Removal Impairment Provision | AMOUNT | 0..1 | RmvImprProv | | | | Reduced impairment provision during the removal transaction. |
14 | A | 2 | Removal Residual Value | AMOUNT | 0..1 | RmvResiValue | | | | Reduced residual value during the removal transaction. |
15 | A | 2 | Removal Cash Proceeds Amount | AMOUNT | 0..1 | RmvCashPrcdsAmt | | | | Amount of cash proceeds received from the removal transaction. |
16 | A | 2 | Removal Non Cash Proceeds Amount | AMOUNT | 0..1 | RmvNonCashPrcdsAmt | | | | Amount of non-cash proceeds received from the removal transaction. |
17 | A | 2 | Removal Expense | AMOUNT | 0..1 | RmvExpns | | | | Expense generated from the removal transaction. |
18 | A | 2 | Unrealized Gain Loss Amount | AMOUNT | 0..1 | UnrlzdGainLossAmt | | | | Amount of the unrealized gain/loss recorded on the Balance Sheet of the removal transaction. |
19 | A | 2 | Realized Gain Loss Amount | AMOUNT | 0..1 | RlzdGainLossAmt | | | | Amount of realized gain/loss recorded on the Income Statement related to the removal transaction. |
20 | A | 2 | Functional Currency Code | CURRENCY CODE | 0..1 | FuncCurCd | | BAS CURRENCY | Currency Code | Functional or group currency related to the balance (in accordance with ISO 4217).Shall match the Currency_Code [CurCd] in the BAS_Currency [BasCur] table. |
21 | A | 2 | Unrealized Gain Loss ACC NUM | GL ACCOUNT NUMBER 100 | 0..1 | UnrlzdGainLossAccNum | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which Balance Sheet amount is recorded for unrealized gain/loss.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
22 | A | 2 | Realized Gain Loss Account NUM | GL ACCOUNT NUMBER 100 | 0..1 | RlzdGainLossAcntNum | | BAS CHART OF ACCOUNTS | GL Account Number | GL account number on which the Income Statement amount is recognized for realized gain/loss.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
23 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
24 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
25 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
26 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
27 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
28 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
29 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
30 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
31 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
32 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
33 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
34 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
35 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
36 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PPE CHANGE | | -- | PpeChng | | | | Contains changes in PPE information not related to additions and removals of PPE. Examples of information changes recorded include revaluation, historical cost, depreciation method and ownership. |
2 | A | 2 | Change ID | IDENTIFIER 60 | 1..1 | ChngId | PK | | | Unique identifier for the change entry.Typically auto-generated by the system. |
3 | A | 2 | PPE ID | IDENTIFIER 100 | 0..1 | PpeId | | PPE MASTER | PPE ID | Unique identifier for the PPE.Typically auto-generated by the system.Shall match the PPE_ID [PpeId] in the PPE_Master [PpeMaster] table. |
4 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Change_Date [ChngDt] occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Change_Date [ChngDt] occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
6 | A | 2 | Tag Number | TEXT 60 | 0..1 | TagNr | | | | Tag that used to be commonly used when there was no ERP system to record the PPE's state of the whole lifespan. It is still used by some ERP systems in the business of PPE.This number is usually generated by manual input or is system-generated.EXAMPLE When there is a PPE, a tag is created correspondingly. Each tag contains either one PPE or several PPEs. However, each PPE has its own PPE_ID [PpeId] as a unique identifier. If a tag only has one PPE, the PPE_ID [PpeId] is the same as the Tag_Number [TagNr]. |
7 | A | 2 | Change Type Name | TEXT 60 | 0..1 | ChngTypNm | | | | Type of change transaction, except for addition or removal transactions.EXAMPLE Re-evaluations, changes in historical cost, changes in depreciation method, transfers, changes in status. |
8 | A | 2 | Change Date | DATE | 0..1 | ChngDt | | | | Date when the changing transaction happens. |
9 | A | 2 | Change Reason | TEXT 200 | 0..1 | ChngReason | | | | Reason why the changing transaction happens. |
10 | A | 2 | Content Before Change | TEXT 60 | 0..1 | ContBefChng | | | | Content (e.g. the method, amount, quantity) before changing transaction. |
11 | A | 2 | Content After Change | TEXT 60 | 0..1 | ContAftChng | | | | Content (e.g. the method, amount, quantity) after changing transaction. |
12 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
13 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
14 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
15 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
16 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
17 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
18 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
19 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
20 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
21 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
22 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
23 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
24 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
25 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |
No | T | N | Business Term | Domain | Card | Tag | PK | Ref. entity | Ref. attribute | Description |
1 | E | 1 | PPE DEPRECIATION | | -- | PpeDepre | | | | Contains the information correlating with PPE summarized depreciation in the period. |
2 | A | 2 | PPE ID | IDENTIFIER 100 | 1..1 | PpeId | PK | PPE MASTER | PPE ID | Unique identifier for the PPE.Typically auto-generated by the system.Shall match the PPE_ID [PpeId] in the PPE_Master [PpeMaster] table. |
3 | A | 2 | Fiscal Year | YEAR IDENTIFIER | 0..1 | FiscYr | | BAS ACCOUNTING PERIOD | Fiscal Year | Fiscal year in which the Created_Date occurs.The year shall be shown in four digits as YYYY, which is part of the extended format and the YYYY-MM-DD from ISO 8601-1.Shall match the Fiscal_Year [FiscYr] in the BAS_Accounting_Period [BasAcntingPer] table. |
4 | A | 2 | Accounting Period | PERIOD IDENTIFIER | 0..1 | AcntingPer | | BAS ACCOUNTING PERIOD | Accounting Period | Accounting period in which the Created_Date occurs.EXAMPLE W1-W53 for weekly periods, M1-M12 for monthly periods, Q1-Q4 for quarterly periods, from any beginning date to any ending date.Shall match the Accounting_Period [AcntingPer] in the BAS_Accounting_Period [BasAcntingPer] table. |
5 | A | 2 | Depreciation Method ID | IDENTIFIER 60 | 0..1 | DepreMthdId | | PPE DEPRECIATION METHOD | Depreciation Method ID | Field used to specify the depreciation method.Typically auto-generated by the system.Shall match the Depreciation_Method_ID [DepreMthdId] in the PPE_Depreciation_Method [PpeDepreMthd] table. |
6 | A | 2 | Useful Life | NUMBER 4 | 0..1 | UsefulLife | | | | Total useful life of the PPE in months. |
7 | A | 2 | Useful Life Remaining | NUMBER 4 | 0..1 | UsefulLifeRmng | | | | Remaining useful life of the PPE in months as of the report date. |
8 | A | 2 | Original Cost | AMOUNT | 0..1 | OriginalCost | | | | Original cost of the PPE. |
9 | A | 2 | Residual Value | AMOUNT | 0..1 | ResiValue | | | | Residual value of the PPE as of the report date.Typically calculated by an expected residual value ratio. |
10 | A | 2 | Depreciable Basis | AMOUNT | 0..1 | DprcblBasis | | | | Depreciable basis of PPE, which shows the difference between the original cost and residual value. |
11 | A | 2 | Depreciation Amount | AMOUNT | 0..1 | DepreAmt | | | | Amount of depreciation recognized during the period. |
12 | A | 2 | Accumulated Depreciation | AMOUNT | 0..1 | AccumDepre | | | | Accumulated depreciation of the PPE as of the report date. |
13 | A | 2 | Carrying Amount | AMOUNT | 0..1 | CarryingAmt | | | | Carrying amount of PPE as of the report date, which shows the difference between the original cost and accumulated depreciation. |
14 | A | 2 | Depreciation Account Number | GL ACCOUNT NUMBER 100 | 0..1 | DepreAcntNr | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the Income Statement amount is recognized for depreciation.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
15 | A | 2 | Accumulated Depreciation ACC NUM | GL ACCOUNT NUMBER 100 | 0..1 | AccumDepreAccNum | | BAS CHART OF ACCOUNTS | GL Account Number | Number of the GL account on which the Balance Sheet amount is recognized for accumulated depreciation.This number is generated either by manual input or by the system.Shall match the GL_Account_Number [GlAcntNr] in the BAS_Chart_Of_Accounts [BasChartOfAcnts] table. |
16 | E | 2 | CREATED | | 0..1 | Crea | | | | Information about the data that was created into the system. |
17 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
18 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
19 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
20 | E | 2 | APPROVED | | 0..1 | Aprv | | | | Information about the data was approved within the system. |
21 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
22 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
23 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
24 | E | 2 | LAST MODIFIED | | 0..1 | LstMdf | | | | Information about the data was last modified within the system. |
25 | A | 3 | User ID | IDENTIFIER 25 | 0..1 | UserId | | BAS USER | User ID | The unique identifier for the person who did the activity. Typically auto-generated by the system. Shall match the User_ID [UserId] in the BAS_User [BasUser] table. |
26 | A | 3 | Date | DATE | 0..1 | Dt | | | | The date of activity. This should be a system generated date (rather than user-created date), when possible. This is sometimes referred to as the creation date. |
27 | A | 3 | Time | TIME | 0..1 | Tm | | | | The time of handling. |
28 | E | 2 | BUSINESS SEGMENT | | 0..n | BusSg | | | | Contains associated Business Segment information. |
29 | A | 3 | Business Segment Code | IDENTIFIER 25 | 0..1 | BusSgCd | | BAS BUSINESS SEGMENT | Business Segment Code | Contains a code to identify the associated business segment. Must match the Business_Segment_Code [BusSgCd] in BAS_Business_Segment [BasBusSg]. |