Business Function Data Structures

You must have a business function for each level break message. Each business function requires an attached data structure. Do not confuse the business function data structure with the text substituted data structure that you created for the data dictionary item. The difference between the two is that the business function data structure moves data variables to the level break function. The data structure for the data dictionary items stores data that is mapped to the text substituted variables.

Include these items in the business function data structure:

  • All data items that are required for the level break text substitution message.

  • All data items that are required for the message to be active; that is, any variables that are required to load the form for the appropriate application.

  • Data item EV01.

    Change the variable name from cEverestEventPoint01 to cIncludeInterconnect. This parameter is a flag that determines if the message is active. This parameter should be included as a parameter in all level break messages, even if the original intent is not to call an application. You must enter a 1 in the data structure value to launch an application.

  • Data item GENLNG.

    Change the variable name from idGenericLong to idGenlong. Use this parameter to control all JD Edwards EnterpriseOne Work Center messaging. This data item is intended for use as a work field for the system.

For the system to return the correct batch number and the amount that is out of balance, the business function data structure must include these fields:

  • Document number

  • Document type

  • Document company

  • Batch number

  • Batch type

  • Document pay item

Two additional data items are required in this data structure:

  • J.D. EnterpriseOne Event Point (EV01).

    Required to determine if the message is an action message.

  • Generic Long (GENLNG).

    Required to control JD Edwards EnterpriseOne Work Center messaging.

The name of this data structure should include the same unique number that is used for the associated data dictionary glossary item. This number is to be appended to the prefix DLM. For example, you should name a business function data structure that was created for level break message LM5509 as DLM5509.