Synchronization Management OMS and EOL

API calls refer to requests made by a client application to a server through an API (Application Programming Interface).
An API call typically involves sending a request from a client application to a server, which then processes the request and returns a response.

API calls are used to access and interact with the functionality provided by an API. For example, a client application may make API calls to retrieve data, perform operations, or execute specific tasks offered by a web service or software platform.

Each API call consists of several components, including:

1. HTTP Method: Specifies the type of action to be performed (e.g., GET, POST, PUT, DELETE).
2. Endpoint: The URL or path that identifies the specific resource or operation being accessed.
3. Request Parameters: Additional data sent with the request, such as query parameters or request body.
4. Headers: Additional information sent with the request, such as authentication tokens or content type.
5. Response: The data or result returned by the server in response to the API call.

API calls are fundamental to integrating different software systems, allowing them to communicate and exchange data seamlessly. They enable developers to build powerful and flexible applications by leveraging the functionality provided by external APIs.

Example: Postman

Step 01 Action

1. Check OMS > Stock reconcillation (ERP) if report is not available kindly notify Luis or Gab
2. Check the number of stock differences 
3. Go to System and Integration
4. Connection > EOL OAuth (See details)
5. Look for Limits
6. Here you can see the list of API Calls that they have. Input this to your work notes add value of (LIMIT) and (Current) for a Day. 
   
7. ​Be guided by the screenshot below:
   
    
8. When doing a Sync its 1 API call per Item
9. Check server task if StockPosition to SQLPut ItemProperty task is already setup
10. Add to your work notes. Check if the quantity of all items that has differences compared to EOL 
11. Once done, escalate ticket to Line 2 
12. Line 2 will plan a schedule to do stock count with the customer so they can check when there is a stock difference. Then they will have a baseline to know how far they need to check the back log.
13. Note that this has to be done after the client's working hours.

Step 02 Additional Note

Synchronization cannot be started if there are orders "open" in Bizbloqs.
Completely new is no problem. Back orders, and completed orders are also no problem.
Orders in the process of picking or parked have an open registration that prevents the synchronization from starting.

The duration of synchronization depends on processing by Exact. This can take between minutes and hours. During this time the scanners cannot be used. For this reason, it needs to be done after their working day.

Stockcount = Is an XLS file list of item here with the data of the correct quantity of and once imported this wouldbe the end results in the data of OMS.

Stocksync = Whats currently in OMS it will make a stock count file and then send that file to Exact 

Reference Ticket: https://support.bizbloqs.eu/agent/bizbloqs/bizbloqs-support/tickets/details/20981000955496543