Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This chapter describes the additional and miscellaneous modifications made to Cinch Document Exchange.
This chapter contains the following sections:


Anchor
_Toc401219356
_Toc401219356
Anchor
NewCSVProcessMfgImport
NewCSVProcessMfgImport
New CSV ProcessMfg Import 01
CSV ProcessMfg Import is an adapter used to convert lines in a csv document to an AgXML document for use by the Process Manufacturing Import service and places them in the designated path.

  1. Process Manufacturing Import
  2. Service Line Settings
  3. Message Label Extension
        1. The file extension of the export file.
  4. ProcessMfg Port Type, ProcessMfg Port URL and ProcessMfg Req Path
        1. These settings need to match Process Manufacturing Import header settings for this service.

...


Anchor
_Toc401219357
_Toc401219357
Anchor
NewProcessManufacturingImport
NewProcessManufacturingImport
New Process Manufacturing Import
Process Manufacturing Import has been created to import manufacturing data and create Process Manufacturing transactions within Cinch. A process manufacturing transaction will be created based on the provided Recipe ID and Quantity. The system will go to the Recipe to determine the "Consumed" and "Produced" line item details.

  1. Process Manufacturing Import
  2. Service Line Settings
  3. Batch by Hour
              1. The Date/Time that will be used in the determination of the batch will come from the Process Manufacturing transaction itself. (Unlike other CinchX services where this is based on the system date and time).
              2. System will append a number at the end of the batch indicating which timeslot the batch is for.
                1. Example, if system is setup to create a new batch every 6 hours, Tickets that are imported with transaction time from 12:00 am to 6:00 am will have a "00" at the end of the batch number, transaction with times from 6:01 to 12:00 noon will have "06", tickets from 12:00 noon to 18:00 will have "12", transaction with times from 18:01 to 23:99 will have a "18".
              3. If no transactions are imported during a particular timeslot, the system will not create that batch.
              4. If setting is left blank, the hours will not be included in the batch number.
  4. Batch Prefix
              1. Default = PRCMF
              2. The transaction will be saved in a batch with a format of BBXXMMDD (BB is the Branch prefix, XX is the Batch prefix, and MMDD is the user date (MM= Month and DD= Day) of the transaction import.
              3. Maximum number of characters 15, this includes the branch prefix, the batch prefix and the date suffix.
              4. If the batch does not exist it will be added
  5. Default Activity Code
        1. If the Activity Code is included within in file line detail, it will be placed on each transaction line.
        2. The Activity Code to place on each transaction line in the event it is not provided with in file line detail.
        3. If Activity Code is not provided or the service setting is not set it will be left blank on the transaction.
  6. Default Apply Cost
        1. If the Apply Cost is included within in file line detail, it will be placed on each transaction line.
        2. If line detail is not provided the Apply Cost from the Recipe will be used.
        3. If the Recipe does not have the Apply Cost defined the Default Apply Cost will be used on each transaction line.
  7. Default Branch
        1. A valid branch ID is required. All transactions will be created within this branch.
  8. Default Cost Method
        1. If the Cost Method is included within in file line detail, it will be placed on each transaction line.
        2. If line detail is not provided the Cost Method from the Recipe will be used.
  9. Default Location
        1. If the Site is included within in file, it will be placed on each transaction line.
        2. If the Recipe does not have the Site defined the Default location will be used on each transaction line.
        3. A valid Site is a required to process the transaction.
  10. Default Work Center
        1. If the Work Center is included within in file line detail, it will be placed on each transaction line.
        2. The Work Center to place on each transaction line in the event it is not provided with in file line detail.
        3. If Work Center is not provided or the service setting is not set it will be left blank on the transaction.
  11. Use Partner Doc#
        1. Yes when selected the MfgNumber included within the import file will be used. Defaults to Yes. When set to Yes, if this is not present the message will fail within Doc Monitor for missing number.
        2. No when selected the next Mfg Number will be used. If line details are not present this must be set to No.
  12. Use Recipe Qty As Actual Qty
        1. Yes when selected will use the RecipeQty as the actual qty of the transaction. Defaults to Yes.
        2. No when selected will use the quantities of the line details as the total actual quantity.
        3. If there are no line details provided, the system will make the Actual Qty equal to the Recipe Qty.
  13. User ID
              1. This is used to set the Cinch transactional user.
              2. Document is created/updated on behalf of the specified user. This must be a valid Microsoft Dynamics GP user.
              3. If blank, User ID specified in CinchX Global Settings will be used.

...


Anchor
NewLotAnalysisImport
NewLotAnalysisImport
Anchor
_Toc401219358
_Toc401219358
New Lot Analysis Import
Lot Analysis Import has been created to import Lot Analysis records from an XML file and create Lot Analysis transactions within Cinch.

  1. Lot Analysis Import
  2. Service Line Settings
  3. Default Branch
        1. A valid branch ID is required. All transactions will be created within this branch.
  4. User ID
              1. This is used to set the Cinch transactional user.
              2. Document is created/updated on behalf of the specified user. This must be a valid Microsoft Dynamics GP user.
              3. If blank, User ID specified in CinchX Global Settings will be used.
            1. Auto generate TestID
              1. Yes when selected the processor will create a new Test ID if one is not present in the xml document. If one is present in the xml document it will be used.
              2. No when selected an error will be thrown if a Test ID is not included in the xml doc.

...


Anchor
ChangestoTouchPointImport01
ChangestoTouchPointImport01
Anchor
_Toc382991878
_Toc382991878
Anchor
_Toc401219359
_Toc401219359
Changes to TouchPoint PO Import 01
TouchPoint PO Import 01 has been modified with the option to allow records to be imported to a database or creating a Purchase Order.

  1. TouchPoint PO Import 01
    1. New Service Settings
      1. Create Purchase Order
        1. Yes, when selected the processor will export CIDX Order Create documents to be consumed by CIDX Purchase Order Import.
        2. No, when selected the TouchPoint data will be directly inserted into Cinch tables where custom reports will be able to access the data. Default = No

...


Anchor
NewExcelloadImport04
NewExcelloadImport04
Anchor
_Toc401219360
_Toc401219360
New Excel Load Import 04
Excel Load Import 04 has been created to take in the Murex Excel file and parse each line into an AgXML 4.0 Load record.

  1. Excel Load Import 04
  2. Service Line Settings
  3. Load Port Type, Load Port URL and Load Port Req Path
        1. These settings need to match load import header settings for this service.
        2. E-Markets support will guide you through the process of setting up this service. Please DO NOT change these setting prior to contacting support.
  4. Message Label Extension
              1. The file extension of the export file.
                1. This extension can be anything but recommended to use XML for easy viewing in IE. (Example: load 1234 will write a file called 1234.xml).
            1. Excel Worksheet Name
              1. This is the name of the specific worksheet in the Excel spreadsheet where the import information can be found.

...


Anchor
NewCSVTradeImport01
NewCSVTradeImport01
Anchor
_Toc401219361
_Toc401219361
New CSV Trade import 01
CSV Trade Import 01 has been created to take in the Murex file and parse each line into an FIXML 5.0 Trade Import record.

  1. CSV Trade Import 01
  2. Service Line Settings
  3. Trade Port Type, Trade Port URL and Trade Req Path
        1. These settings need to match the trade import header settings for this service.
        2. E-Markets support will guide you through the process of setting up this service. Please DO NOT change these setting prior to contacting support.
  4. Message Label Extension
              1. The file extension of the export file.
                1. This extension can be anything but recommended to use XML for easy viewing in IE. (Example: trade 1234 will write a file called 1234.xml).

...


Anchor
ChangestoFIXML50TradeImport
ChangestoFIXML50TradeImport
Anchor
_Toc401219362
_Toc401219362
Changes to FIXML 5.0 Trade import
FIXML 5.0 Trade Import has been modified with new translations to handle the CSV Trade Import 01.

  1. FIXML 5.0 Trade Import


Processing Note:

...


Anchor
_Toc401219363
_Toc401219363
Anchor
ChangesToAgXML40TicketImport
ChangesToAgXML40TicketImport
Changes to AgXML 4.0 Ticket Import
AgXML 4.0 Ticket Import has updated to support updating grades on a posted scale ticket.

  1. AgXML 4.0 Ticket Import
  2. Service Line Settings
  3. Update Destination Grades Only
        1. Yes, when selected the processor will only update records within the IRGNTicketGradeWORK table. After the grades are updated, discounts will be recalculated and DPR adjustment records will be created if needed. Also the response ticket that is normally exported (containing the new ticket number), will not be exported.
        2. No, when selected records are imported to create/update tickets normally.
      1. Get document identifier from
        1. The setting is used to select which section of xml to use when looking for the document identifier. This will not be used as the ticket number, it will be used to identify that the file has been imported and recorded in the number key status table. This gives the Grades Only import more flexibility when searching for the previously imported ticket.
        2. Available options are Buyer, Seller, and File Name
          1. File Name will not work if the Ticket Import and Grade Ticket Import files are not the same.
      2. Grades Only – Original Partner
        1. Since it is required that the Grades Only import uses a separate service partner than the normal ticket import, this will only be set on the grade import service partner to identify the original service partner.
        2. Enter the PartnerID (not the name) of the pipe used to import the original ticket.

...


Anchor
_Toc401219364
_Toc401219364
Anchor
CSVShipmentImport
CSVShipmentImport
New CSV Shipment Import 02
CSV Shipment Import 02 has been created to take in the Kennedy scale file and parse each line into an AgXML 4.0 Shipment record.

  1. CSV Shipment Import 02
  2. Service Line Settings
  3. Shipment Port Type, Shipment Port URL and Shipment Port Req Path
        1. These settings need to match shipment import header settings for this service.
        2. E-Markets support will guide you through the process of setting up this service. Please DO NOT change this setting prior to contacting support.
  4. Message Label Extension
              1. The file extension of the export file.
                1. This extension can be anything but recommended to use XML for easy viewing in IE. (Example: shipment 1234 will write a file called 1234.xml).

...