Requested Exceptions for Integration Transactions (tfgld4585m000)

Use this session to enter or approve requests to post integration transactions to specific financial periods.

Requests for exceptions can be created for integration transactions that cannot be logged and posted because the financial period that corresponds with the transaction date is Closed.

You can enter the fiscal year and period, the reporting year and period, and/or the tax year and period to which the integration transaction must be posted. Only the fields that correspond to a Closed period are enabled.

Note: 

LN checks the status of the period type on which you want to base the closed period handling for integration transactions.

You can select the default period type in the Check Period Status on field of the Integration Parameters (tfgld4150s000) session and the period type for the individual integration document types in the Period Handling by Integration Document Type (tfgld4579m000) session.

If you select the Create automatic exception requests check box in the Period Handling by Integration Document Type (tfgld4579m000) session, LN automatically creates exceptions requests. You can use this session to view and authorize the requests.

To approve a request, select the request and on the appropriate menu, click Appr Exceptions. The Approve Requested Exceptions for Integration Transactions (tfgld4585m100) session starts. If you are authorized to run this session, you can approve the requests.

Exception requests for inventory transactions

If you confirm a receipt in warehousing, LN creates an Inventory integration transaction for business object whinr100. The receipt is identified through a generated sequence number.

You cannot create an exception request for an Inventory integration transaction because you do not know the business object ID, which is the generated sequence number. For this reason, you must create an exception request for business object whinh310, Warehouse Receipt.

To post inventory transactions to specific periods, depending on the type of inventory transaction you must create an exception request for one of the following business objects:

  • Warehouse Receipt (whinh310)

    The business object ID is the receipt number.

  • Warehouse Management Loads and Shipments (whinh440)

    The business object ID is the load number or the shipment number.

  • Cycle Count Order (whinh500)

    The business object ID is the order number.

  • Adjustment Order (whinh520)

    The business object ID is the order number.
Note: You can only create requests for exception if the Closed Period Handling option for the integration document type is Exception handling.

Field Information

Sequence Number

The generated sequence number of the request.

Business Object Company

The logistic company in which the integration transactions are generated.

Financial Company

The financial company in which the integration transaction is posted.

Business Object

The business object of the integration transactions for which you enter the request.

Business Object ID From

The Business Object ID From and the Business Object ID To fields define the range of transactions for which you enter the request.

Original Fiscal Year / Period

The fiscal year and period in which the transaction was created.

Target Fiscal Year

The fiscal year and period to which you want to post the transactions.

If the fiscal period that corresponds with the transaction date is Open, LN posts the transaction to the period. You cannot change the year and/or the period.

Target Reporting Year

The reporting year and period to which you want to post the transactions.

If the reporting period that corresponds with the transaction date is Open, LN posts the transaction to the period. You cannot change the year and/or the period.

Target Tax Year

The tax year and period to which you want to post the transactions.

If the tax period that corresponds with the transaction date is Open, LN posts the transaction to the period. You cannot change the year and/or the period.

Requested by

The employee who entered the request.

Reason

The reason for the request. Before you can save the request, you must enter a reason.

Description

The description or name of the code.

Approved till date

The expiry date and time of the approval.

After this date and time, you cannot apply the exception.

Approved by

The employee who approved the request.

Related topics