DynDeveloper.com

The SY00500 is unusual in that it is used slightly differently for each module.

Bill of Materials

Payables

Payables Management Payments Entry

Inventory:

Dynamics posting relies upon the Batch Activity File (SY_Batch_Activity_MSTR) and the 'Batch Status' field in the Posting Definitions Master File (Batch_Headers) to prevent users from accessing transactions that have been prepared for posting.

When a user selects a batch to post, Dynamics sets the 'Batch Status' field in the batch's corresponding Batch_Headers record to the constant BATCH_POSTING, indicating that the batch is ready for posting. At this point, the user cannot edit transactions in the batch unless they unmark the batch, at which time the status changes to OKAY. See the field values for 'Batch Status' in the following Field Descriptions for descriptions of these constants.

When posting starts, Dynamics adds an activity record to the SY_Batch_Activity_MSTR file, indicating that the batch is posting. This record also tracks the batch source, transaction source, and batch number for the batch. This record remains in the Dynamics system as long as the batch continues to post.

When posting and printing are complete, Dynamics removes the activity record from the SY_Batch_Activity_MSTR file (if the batch isn't recurring), and clears the 'Batch Status' field in the Batch_Headers record. No access violations will occur when a user is updating the transaction or any distributions associated with it, since the batch activity record locks all users out of the batch that's being posted.

Dynamics uses the Batch_Headers file according to the following guidelines:
- Marking a batch to post sets the Batch Status field to BATCH_POSTING, or 1. When a user begins posting transactions, Dynamics creates a batch activity record for the marked batch.
- The user can't delete or edit the batch or the transactions in the batch if the Batch Status field has a marked status (field values 1-3).
- When a user deletes a batch, it's important that you delete the batch header record last, since the flag on that record stops other users from accessing the batch.

How IV uses the Batch_Headers file
Each transaction in the IV_TRX_WORK_HDR file must be assigned to a batch. The batch header record for the batch should exist before any transactions are added to the work file for the batch. The 'Batch Status' of the batch header record should be set to BATCH_RECEIVING while any transactions are being added to the system from an outside source. Also, there should be a record added to the SY_Batch_Activity_MSTR file. This record should have the 'Posting' field set to true, thereby preventing other users from working in the batch until the transfer has been completed.