Requests, save without checking

Saves the data entered in a request without checking data consistency.

Check

Checks the consistency of the data entered. The system checks for instance whether the total of individual documents corresponds with the overall amount. This is for your information only. This is not necessary technically as the system carries out a consistency check in any case when setting the “Complete” indicator.

Complete

Controls the processing method of the request: only completed requests can be approved or rejected; only incomplete requests can be deleted. Besides this, the “Complete” indicator has the effect that the document participates in the active availability control and is updated. Updating means that the funds commitment is reduced and the budget is debited.

Complete documents are always consistent because the system checks if the document is really complete when setting the indicator.

See also: Set Request as Complete

Release transaction

Sets the processing status of the document to “approved” or “rejected”. Only complete requests can be approved or rejected. As soon as the request is approved, it can no longer be changed.

See also: Approve (Release) Request

Release of Requests in Workflow

automatically controls the entire approval procedure in Workflow. The approval procedure must be defined in Customizing.

See also: Releasing Requests in Workflow

Bundling FI documents

allows parked FI documents from components Financial Accounting , Materials Management and Funds Management to have a request number assigned to them. This means the FI documents can be approved either manually or via an approval Workflow.

See also: Bundling FI Documents

Print

The printed hard copy of a request can be used for the approval procedure. It not only contains some of the information entered, but also the signature fields “functionally correct”, “mathematically correct” and “arranged by”

Posting

Can take place as soon as the request has been approved. When a request is posted in the Funds Management component, the program sets the posting day in the document header of the posted request; through this is it possible to display it in day-end closing.

See also:

Post Request

Copying

Copies the document entered. This changes the total amount of the request and the number of documents assigned to this request number. You see this number in the request at the bottom on the right, under: Item 2/2 means that you are on the second (and last) document of this request.

The copy function facilitates for example the creation of collective requests.

Adding documents

Adds a new document to the request. In contrast to the copy activity, the system only transfers the header data for the new document, not the line items. So you choose this function if different account assignments or subledger accounts are used in the individual documents.

Reverse entry

Resets the screen content to how it was before the last screen processing. You can therefore reverse entries as long as they have not yet been processed by the system.

Delete

Deletes individual documents from a request. If the individual document has not yet been saved in the database before deletion, the document is deleted immediately. If the document was already saved in the database, the system only sets the amount of the deleted individual document to 0. As soon as the request is set to the status “Complete”, all individual documents with amount 0 are removed from the request.