Importing Business Transactions - Overview

Business Line Import is a method of importing business transactions, for example, purchase orders and sales orders, in bulk and creating Financials journals. This differs from the regular Ledger Import function in that Order Fulfilment reference data can be used when importing, as if the posting is coming from an Order Fulfilment module and creating a journal.

This can be used when an external application is used instead of SunSystems Order Fulfilment purchasing, sales or inventory modules, and when SunSystems Financials is being used. The data to be used in the ledger posting may depend on item, supplier, warehouse etc, which are held in the Order Fulfilment system. Business Line Import determines the correct account code to be used and posted to inancials, as if it were carrying out an Order Fulfilment ledger posting.

Business Line Import uses Order Fulfilment Ledger Interface structures and processes, and the SunSystems Connect (SSC) component BusinessLineImport.

  1. Specify this information:
    SSC Component Input
    SSC BusinessLineImport component is available. The external application sends an input payload to the SSC component.
    Ledger Interface
    The SSC component calls Business Line Import. A ledger interface record must exist and be defined in the input payload. The ledger interface record defines how the journal is created and is mandatory in the input payload. The ledger interface record must be of the type External/Business Line Import Values. The SSC component calls Business Line Import. A ledger interface record must exist and be defined in the input payload. The ledger interface record defines how the journal is created and is mandatory in the input payload. The ledger interface record must be of the type External/Business Line Import Values.
    Journal Lines
    The journal lines are created as defined in the ledger interface record. This is identical to a journal being created from an Order Fulfilment posting.
    Account Codes

    The ledger interface record defines the account codes to be used when creating the journal. If an account code is to come from the item master, warehouse, supplier, etc, that is, the ledger interface account recognition codes, then the system determines this.

    Uwaga: The item, warehouse, supplier, etc, record must be defined in the input payload, and be valid codes in SunSystems.
    Values

    The values to be posted to the journal must be defined in the input payload. Order Fulfilment value labels and formulae are not available. However, the purchase and sales prices on the item master can be used.

    Uwaga:  The system makes no assumptions as to the currency of the values in the input payload. The values against the correct currency type must be specified in the ledger interface, whilst adhering to the posting rules defined in the Journal Type (JNT) and Business Unit Setup.
    Analysis

    Any analysis to be entered on the journal lines is determined by the existing Order Fulfilment processing, that is, analysis can be obtained from any one of the elements shown below, in the following order:

    • Ledger Interface - suppress analysis. No analysis is entered on the journal.
    • Ledger Interface - replace analysis. Any analysis is replaced with a fixed code.
    • Business Line Import SSC input payload - as specified on the Ledger Interface.
    • Analysis Mapping to Ledger (ANM) defines analysis from item, customer, supplier, and so on.
    Transfer Data Codes
    The journal transaction date, journal source, transaction reference and description are defined on the ledger interface.
  2. Save your changes.