Version: eXtendMultiFulfillment all versions
Audience: All
Overview
eXtendMultiFulfillment processes queue records using two methods:
- Real-time Processing
- Scheduled Processing
Scheduled Processing Details
Scheduled processing uses two different methods based on the number of pre-fulfillment records and amount of NetSuite processing available:
- eXtendMultiFulfillment Queue Processing Map Reduce
- Used when all pre-fulfillments can be created in a single process run.
- Used when all pre-fulfillments can be created in a single process run.
- eXtendMultiFulfillment M/R Chained
- Used when pre-fulfillments need to be created across multiple process runs.
- Used when pre-fulfillments need to be created across multiple process runs.
Processing Criteria
The type of processing depends on:
- Number of Map/Reduce Processors Available
- Number of Pre-fulfillment Records
Scenarios
- Smaller pre-fulfillment count:
- If a Map/Reduce processor is available and can be completed in a single process run, records are processed in real-time.
- If a Map/Reduce processor is available and can be completed in a single process run, records are processed in real-time.
- Larger pre-fulfillment count:
- If a Map/Reduce processor is available but cannot be completed in a single process run, the first batch of records are processed in real-time, and the rest are queued for the next run of scheduled processing.
- If a Map/Reduce processor is available but cannot be completed in a single process run, the first batch of records are processed in real-time, and the rest are queued for the next run of scheduled processing.
- No Map/Reduce Processors Available:
- The entire process is queued for the next run of scheduled processing.
- The entire process is queued for the next run of scheduled processing.