MarketMan <> Oracle Fusion Integration 

Guidelines: 

Purchase Flow:

1. Received Purchase Orders are reflected in Oracle Fusion as Vendor Bill with each line item classified to Food, Beverage or Other. 

2. Negative values on MarketMan are reflect as debit note on Oracle Fusion.

3. Condition for Purchase Orders integration is DocType: invoice and DocStatus: approved.  

4. Line description in the vendor bill indicates that the bill is created by the integration and includes Marketman DocNumber as reference. 

5. All new Vendors should be created in Marketman only and they will be synced to Oracle Fusion by the integration. 

Transfer Flow:

1. Transfer transactions are reflected as Journal Entries in Oracle Fusion. 

2. All transfer orders from a specific location for a specific day can be found in the same Journal. 

3. Each line in the Transfer Orders Journal represent a transfer order total of Food or Beverage specified in the line memo. 

4. Marketman Transfer Order Number can be found in the line memo of the Journal Entry. 

Wastage Flow:

1. Waste events per location are reflected as Journal Entry in Oracle Fusion with the total waste of Food and Beverage each in a separate line indicated in the line memo. 

2. Waste events with the description Staff meals / drink are reflected in Oracle Fusion as Journal Entry representing the staff meals. 

Memo in all Journal Entries indicates that the record is created by the integration and line memo gives more information about the type of the transaction and category of items. 

Trouble Shooting: 

1. Some Purchase Orders not Integrated. 

Reason: Document created in a day and approved in a day passed the integration date.  

Solution: At the end of the month the Integration will read all Purchase Orders of the month and sync the missed orders. 

2. Differences in Transfers, Waste Events or COGs 

Reason: Modification by an employee on Marketman transaction after data is synced the Integration.