Attributes

To use the IGFC pages correctly, the specific master data BODs must be registered with the complete attributes. For example, Chart of Accounts Mapping and Dimension Code Assignments need the AccountingChart and the ChartOfAccounts BOD mappings. Currency Rate Type and Accounting Journal BOD mappings are required if setting up Currency Rate Type Assignments. CodeDefinition BOD mapping is required if Dimension Code Assignments uses this document as a source of dimension values.

See Attributes for BOD Mapping in IGFC for the attributes to be mapped.

Attributes are elements of a business document that contains data. In registering a business document, you must select the attributes that are used in the different configurations and rules for generating output business documents.

You must create more than one registration depending on the number of a document's components, repeating components, and repeating attributes within components. For example, the invoice document is comprised of the InvoiceHeader and InvoiceLine components. The InvoiceLine component can repeat because an invoice can contain multiple lines. Within an invoice line, there can be several items.

<InvoiceHeader>
             <DocumentID>
                 <ID>INV-001</ID>
                 <DocumentDateTime>2013-03-27T06:56:52Z</DocumentDateTime>
             </DocumentID>
        </InvoiceHeader>
        <InvoiceLine>
          <LineNumber>1<LineNumber>
          <Item>
            <ItemID>
               <ID accountingEntity="AE1" location="Loc1">1001</ID>
            </ItemID>
            <ItemID>
               <ID accountingEntity="AE1" location="Loc1">1002</ID>
            </ItemID>
         </Item>
        <Quantity>10</Quantity>
        <UnitPrice>
           <Amount currencyID="USD">100</Amount>
        </UnitPrice>
      </InvoiceLine>
      <InvoiceLine>
         <LineNumber>2<LineNumber>
         <Item>
           <ItemID>
               <ID accountingEntity="AE1" location="Loc2">1003</ID>
          </ItemID>
       </Item>
       <Item>
         <ItemID>
             <ID accountingEntity="AE1" location="Loc2">1004</ID>
         </ItemID>
      </Item>
     <Quantity>5</Quantity>
     <UnitPrice>
        <Amount currencyID="USD">20</Amount>
    </UnitPrice>
  </InvoiceLine>

In the invoice business document example above, there are three groups of registrations: for the invoice header attributes, for the invoice line attributes, and for the invoice line item attributes. A grouping element must be specified for each registration. This refers to the root attribute that does not have a value but contains all other attributes in the group. The invoice line item component and its attributes have to be registered separately because it occurs multiple times in an invoice line. In registering the invoice line item attributes, it has to be specified that the parent of the invoice line item registration is the invoice line registration.

This table shows sample registrations of the invoice business document with the first attribute as the grouping element:

Business Name	BOD Registration Name	Attributes	Parent
Invoice	InvoiceHeader	invoiceHeader id dateTime	n/a
Invoice	InvoiceLine	invoiceLine lineNumber quantity unitPrice unitPriceCurrency	n/a
Invoice	InvoiceLineItem	invoiceLine itemID accountingEntity location	InvoiceLine

BOD registration and attribute mapping for AccountingEntity and SourceSystemJournalEntry BODs are created during installation. There is no need to register and map these BODs. Modification to the Accounting Entity BOD mappings is not allowed. However, SourceSystemJournalEntry mappings can be modified only to include attribute filters.

See Registering business object documents (BODs).