Use this function to manage the purchase requirements of the different departments or sites of a company. You can create, modify, delete, copy, view, and print delivery requests.

Each purchase request can contain several lines concerning different purchased products regardless of whether they are managed in stock or not.

Moreover, the recorded purchase requests can be:

  • Listed, signed (depending on the setup), closed and displayed during the creation of an RFQ
  • Considered on order entry to be turned into an order

You can modify a purchase request if the following condition are met:

  • The purchase request has not been signed or all the signatures have been canceled (provided the signature management is activated)
  • It has not been closed
  • It has not been turned into an order

When you modifying a purchase request, you can choose any line and click the Actions icon to:

  • Enter text on this line
  • Copy this line
  • View the budget detail
  • Close this line: if you try to close an already closed line, a message is displayed and, if the context enables it, you can reactivate this line (by canceling the closing).

Budgetary and accounting postings

So as to satisfy every company legal context, posted amounts in expense accounts must correspond -depending on cases- to:

  • the ex-tax amount: regular functioning mode of most companies,
  • the ex-tax amount with re-incorporation of the non recoverable VTA amount: banks, insurance companies,
  • to the ex-tax amount with re-incorporation of the totality of the VTA amount: administrations, training, health...

The application is used for the posting of expenses and the generation of pre-commitments, commitments and expenses according to one of theses three options. Corresponding budgetary postings are done according to the same rules.

This commitment mode is determined by the PURCMMTAX - Commitment type parameter (ACH chapter, CMM group). The posting of invoices and credit notes and their budget upload depends on the VAT rate and on the deduction percentage.

SEEINFOThe supplier code contains the tax rule. Purchase requests can be entered without supplier code: therefore, the PURVACBPR- Default tax rule parameter (ACH chapter, CMM group) can be used to stock a default tax rule for the entry of purchase requests, for the company or the site.

Prerequisites

SEEREFERTTO Refer to documentation Implementation

Screen management

The presentation of the entry screen depends on the setup of the chosen transaction.

If a single transaction has been set up, there is no choice suggested. Where more than one transaction have been set up, a window displays the list of transactions that you are authorized to use. Regardless of the transaction, a purchase request is broken down into a section containing header information and a section used to create the different lines.

Home

In the header, enter the general information relating to the purchase request, such as the requester, the site, the request date and the project code.

Requester (field REQUSR)
Code of the requester, initialized by default to the code of the connected operator, and modifiable.
Request site (field PSHFCY)

Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.).
This field is mandatory. It is initialized by default by the purchase site associated with your function profile.
You can modify this code by selecting a code from the list of authorized sites.
Request no. (field PSHNUM)

Purchase order number that allows the order to be identified in a unique way. This number is generated automatically upon each creation according to the sequence number counter setup associated with this type of document.
Request date (field PRQDAT)

The request date is initialized to the current date. It can only be modified in creation mode. If you modify this date, a message is displayed suggesting that you update the prices and potential discounts calculated for the entered purchase request lines.
Project (field PJTH)

Use this field to enter a project code.
The management of this code depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

  • When the value is No, it may be a code selected freely.
  • When its value is Yes, an existence check is systematically applies to the entered project code.
    You can use the Selection icon to display the list of available project codes.

The management rules of this field are based on the PJTSNGDOC - One project by document- parameter (TC chapter, MIS group).

  • When this parameter is set to Yes, the management of multiple projects is prohibited.
    The project code is always the same on the document header and on the lines.
    In direct creation, the project code you enter on the header is always used on the document lines and cannot be modified.
    In case of a document transformation, the project code entered on the header is used to filter the documents available for selection and picking. If not project code is entered, it is automatically loaded with the project code of the first selected document. If you clear this document, the project code is not deleted.
    If you modify the document header project code, this code is automatically used on the lines. A message is displayed and suggests to update the prices/discounts on lines. The update only applies to lines which are not ordered and not closed.
  • When this parameter is set to No, the management of multiple projects is authorized.
    In direct creation, the project code you enter on the document header is used to initialize the project code of the document lines and can be modified.
    In case of document transformation, the project code entered on the header is only used as the default values of lines with no project code.

    If you modify the header project code, a message suggests to transfer this code to the lines of the document, according to the following options:
        • Yes: the project code is transferred to all lines. A second message is displayed and suggests to update the prices/discounts on lines. The update only applies to lines which are not ordered and not closed.
        • No: the project code is not transferred to the lines.
        • Yes if same value: the project code is only transferred to the lines associated to the former project code.
          The project code used on the lines can be the same as that already used on the other lines. As the system is not able to differentiate these lines, no price/discount update is suggested or performed so not to overwrite the prices that the user may have entered, which do not originate from the price list.

Tab Lines

Use this section to identify the product(s) that are the subject of the purchase request. The minimum required information is the product, the required delivery date and the quantity.

Grid

Product (field ITMREF)

This is the internal reference of the requested product, which must be included in the Products table.
The following products cannot be ordered:

  • manufactured products
  • phantom products
  • sub-contract products.

The product description can be modified whatever the product category.

From the Product field, there are many possibilities. You can directly enter the reference of a product which is included in the Products file or click the Actions icon to:

  • Select a product from the file
  • Create the product in the product record, according to your access rights
  • View the orders in progress
  • View and take into account the answers to the existing RFQs if the transaction used allows it Considering an answer to a RFQ is mainly used to initialize information, such as quantity, price, supplier etc.

Once the product reference has been entered, click the Actions icon to limit the list to those elements (RFQs or orders) that are associated to this particular product.

When the entered product is already the subject of an order or a contract, a message is displayed to inform the user whether the line of this contract is still valid or not.

For the products managed in stock, it is possible to take into account the suggestions coming from the MRP calculation (in the Manufacturing module) or those coming from the reorder calculations (in the Stock module).

When there are purchase suggestions for the product entered (POS), a window automatically opens to propose that the requirements be taken into account. If the user does not want to take into account the suggestions, they should exit this window to return to the line entry.

If the user wants to take the suggestions into account, they can enter a date range in order to limit the proposition in time: When no date is entered, the suggestions as a whole are submitted. You can then modify the unit in which the requirements quantities must be expressed: by default the stock unit is suggested. It can be modified provided the new unit is selected from the unit list suggested in the selection (purchase unit, packing unit and stock unit of the product). Requirement lines are then displayed with, for each one:

  • the requirement date, the site, the buyer's code;
  • the requirement quantity along with the quantity taken into account and initialized by default to the quantity of the requirement,
  • various information such as the type and the order number in the WIP.

After entering the unit, you can automatically enter the quantity to be taken into account, which is the only information that can be entered on this screen. If you want to sort the suggested list by requirement date or by site, you must exit the entry mode (click Escape and use the Actions icon to choose the required sort.

The suggested quantity taken into account can be modified on the condition that the quantity entered is less than or equal to the requirement quantity, which can be the case if, for instance, the user wishes to take into account only part of the requirement. If you wish to exclude requirement lines, enter a null quantity.

At the end of this, if at the time of entry of the product, the user has previously selected an invitation to tender response, an additional check is carried out and a warning message appears when the total requirement quantity is less than that mentioned in the response. You can cancel or proceed with your entry.

After validation, the requirement lines taken into consideration are regrouped by site and the corresponding PR lines are automatically generated.

The entry of other data in the line depends on the selected transaction. This is the case for example of the information relating to Site, Supplier and Net price.
Description (field ITMDES)

Main designation of the product issued from the product record and that can be modified during entry. This is the product description translated into the operator's language.
This description is transmitted with any potential modification to the invoice and printed on the order document.

SEEINFO The product record can be accessed from this field using a tunnel.

Standard description (field ITMDES1)

This is the description entered in the product record. This description will be transferred with any modifications to the supplier invoice.

SEEINFO The product record can be accessed from this field using a tunnel.
Product type (field ITMKND)
Receiving site (field PRHFCY)

Specify the site where the goods must be delivered by the supplier. It is initialized to the order site if the latter is also a warehouse.
For a purchase request or an order for a product managed in stock:

  • the receipt site must be a warehouse,
  • the product reference must be defined for this receiving site.

However when the request site is not declared as a warehouse in the site table and the ordered product is managed in stock, it is the first storage site associated with the legal company of the request site that is submitted.

From the Receiving site field, you can:

  • Directly enter a site code, provided it belongs to the same legal company as the requester site. In addition, the existence of the entered site is controlled in the site table;
  • Use the Actions icon to select a site from the submitted list or to carry out different stock inquiries.

SEEWARNING The receipt site must belong to the same legal company as the requesting site for a purchase order or the order site in case of an order.

If you change the receiving site, a message is displayed to suggest you to run the search for the default supplier again:

  • You want to run the search again:
      • If a default supplier is found in the Products - Sites record, this default supplier will populate the PR line.
      • If there is no supplier listed in the Products - Sites record, the default supplier listed in the Products - Suppliers record will be used, except if the ITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) specifies that the product-supplier must be listed at site level.
      • If there are suppliers on the Products - Sites record but no default supplier is found because they are all blocked, the supplier is not populated on the PR line. The field remains empty.
  • You do not want to run the search again:
      • The original supplier is kept.
Requested date (field EXTRCPDAT)

This is the desired receipt date. A check is carried out with respect to the unavailability dates of the reception site. In the case of the site being unavailable on this date, a warning message appears and another date must be entered. The planned due date can also be automatically recalculated when the date entered corresponds to a non-working day for the site: it is then automatically proposed as the first working day before the non working day.

This information is mandatory. A warning message can also be displayed if the date entered comes previous today's date. It is used to initialize the theoretical order date.
PUR (field PUU)

This is the default purchase unit linked to the product. When the supplier is changed, this unit can be adjusted according to the purchase unit defined on the supplier-product record.
The product has two purchase units:

  • purchase unit defined at the level of the unit product record,
  • purchase unit linked to the supplier.

The purchase unit cannot be modified. A re-calculation of the quantities, prices and discounts is then carried out.
This unit is reused on the purchase order.

SEEINFO Upon invoicing of a product, the product PUR is used.

The unit is initialized by default to the purchase unit associated with the product. When an RFQ response has been taken into account, the unit specified in this response is submitted. When this field can be entered, a new unit can be selected in the unit table.
PUR quantity (field QTYPUU)

This section is mandatory.
If the line exists with a null quantity, it will not be taken into account upon validation. In modification mode, validation will be refused.

The quantity must be entered. In effect, a message warns the user that the line will not be created if the quantity remains null at the end of the entry.

A warning message can also appear when modifying the quantity proposed further to the taking into account of the requirements and when the quantity entered is less than the quantity taken into account.
STK (field STU)

This field indicates the product management unit in which the stock is expressed.
STK quantity (field QTYSTU)

This is the quantity in stock unit calculated from the ordered quantity in order unit.
This quantity cannot be directly modified. The coefficient between the PUR and the STK cannot be changed.
Supplier (field BPSNUM)
  • If the PSHINIBPS – PR supplier initialization parameter (ACH chapter, PSH group) is set to ‘Yes’, the supplier is initialized with the default supplier defined in the Product-site record or Product-supplier record as follows:
      • If the default supplier defined on the Product-site record is not 'valid', the field remains empty. You can select a supplier.
      • If there is no supplier listed in the Product-site record, the default supplier listed in the Product-supplier record will be used, except if the ITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) specifies that the product-supplier must be listed at site level. In this case, the field is left blank.

In all cases, as the supplier is not mandatory, you can delete this supplier. You can also modify it.

  • If the PSHINIBPS – PR supplier initialization parameter is set to ‘No’, the supplier is not initialized. If you want to enter a supplier, you must enter this supplier manually.

To enter the supplier, enter the supplier code or click the Actions icon to:

  • Select a supplier in the file.
  • Select a supplier from the list of suppliers suggested for the product.
  • Select a supplier from the list of suppliers for the product-site.
  • Create, according to the user's access rights, a supplier in the file.
  • View the list of the last order prices.

This supplier cannot be defined as a ‘Prospect’ and must be ‘Active’. During the entry, several controls are performed and various messages can be displayed, according to the situations:

  • The supplier is declared to be in dispute. This can be a blocking message or a simple warning according to the value given to the dispute code in the Supplier record.
  • The product is blocked for any purchase request made to this supplier, or to this supplier for the specific receiving site. This can be a blocking message or a simple warning according to the value of the blocking code in the Product-Supplier or Product-Site record.
  • The product is not listed by this supplier. This message can be blocking or constitute a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) general setup.
  • The product is not listed by this supplier for this receiving site. This can be a blocking message or a simple warning according to the value of the ITMBPSFCY - Supplier site referencing parameter. If this message is blocking, you can still proceed with your entry but the Receiving site field must be set as available for entry for the entry transaction. In this case, the Receiving site field is emptied. You must then enter a site where the product-supplier is referenced, or for which the ITMBPSFCY - Supplier-site referencing parameter is not defined as blocking.

When modifying the supplier on a purchase request line, the re-calculation of the prices and discounts according to the price lists defined for the new supplier is suggested. The quantity of the request and the purchase unit can be adjusted according to the purchase unit of the new supplier and if need be according to the rounding rule defined by the PURQTYRND - Purchase quantity rounding general parameter (ACH chapter, ORD group).
Major version (field ECCVALMAJ)

The major version number can only be accessed if the tracking of major versions is activated at product setup level (in the Management section of the Product function, the value of the Stock version field is set to 'Major'). If the versions preloading is activated at the Product-supplier level, or otherwise, at the Product/Order level, the last active major version is preloaded automatically. Otherwise, the last major version with the 'Stopped' status will be preloaded. It can still be modified.
Minor version (field ECCVALMIN)

The minor version number can only be accessed if the tracking of the major and minor versions is activated at product setup level (in the Management section of the Product function, the Stock version field is set to 'Major and minor'). If the version preloading is activated at Product-supplier level, or at least, at Product-Order level, the last minor version is preloaded automatically. It can still be modified.
Project (field PJT)

The management rules of this field are based on the PJTSNGDOC - One project by document- parameter (TC chapter, MIS group).

  • When this parameter is set to Yes, the management of multiple projects is prohibited.
    The project code of the document line is never available for entry. In direct creation, it is loaded automatically with the code entered in the header and cannot be modified.
    If you modify the document header project code, this code is automatically used on the lines.
  • When this parameter is set to No, the management of multiple projects is authorized.
    The project code is initialized on the document line based on the code entered in the header. The following lines can have a different project code.
    You can only modify the project code of lines if entering this field is authorized by the chosen entry transaction.

    If you modify the header project code, a dialog box opens and suggests to transfer this code to the lines of the document, according to the following options:
          • Yes: the project code is transferred to all lines.
          • No: the project code is not transferred to the lines.
          • Yes if same value: the project code is only transferred to the lines associated to the former project code.

    In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory project control parameter.
      • When the value is No, it may be a code selected freely.
      • When its value is Yes, an existence check is systematically applies to the entered project code.
        You can use the Selection icon to display the list of available project codes.
Calculated order date (field EXTORDDAT)

Theoretical order date. It's the result of the following calculation: requested due date less reorder lead-time.

The lead-time is dependent on the price, or the product-site, or the main product.
Net price (field NETPRI)

On a purchase request, the net price can come from a RFQ, a price list or the product record. It is calculated from the gross price and the discounts or charges. It can be modified.

Irrespective of whether the Net price field is present in the screen, the price is initialized based on the value of the PSHVLT - PR line valuation parameter (ACH chapter, PRI group):

- Either to the value of the standard cost of the Product-site record

- Or to the price originating from a price list search In this case, if the price list search has been unsuccessful, the base purchase price (Supply section) of the Product record is taken into account instead. If this is not possible, and only if the value of the PURPRICE - Price by default standard cost parameter (ACH chapter, PRI group) is set to ‘Yes’, the Standard cost of the Product-site record is used.

From the Net price field, click the Actions icon to:

  • View or modify the price, the various charges and discounts and the reasons associated with them
  • View the price lists
  • Reinitialize the price by running a new price list search.

As you enter products in a table, it is possible to list several products. At the end of a line entry, you will automatically be back in entry mode for the next line. At this stage, you can go back to any entered line and click the Actions icon to:

  • Enter text on this line
  • Copy this line
  • View the commitments generated by the PR
  • View the budget detail

According to the setup, budget control can be performed at the level of each line for information purposes or on entry completion.

At the end of a line entry, a warning is given when the budget control on the line has been activated and a budget has been exceeded. This message can be a blocking message or a simple warning depending on the value of the general parameter (see the BUDCNTPRP - Precommitment control type parameter, BUD chapter, CMM group). A similar message may appear when validating the PR.

In addition, when the update of pre-commitments is active, this is carried out automatically:

  • Upon validation of the purchase request, if the signature management is not active (see APPPSH - Manage signatures - PRs parameter, ACH chapter ACH, APP group)
  • On the first signature in the circuit if the purchase request is subject to signature management.

At the end of the processing, a number is assigned to the purchase request and is displayed. Depending on the chosen transaction, the printing of a Purchase request document can be automatically launched after the entry has been completed.
Line amount - tax (field LINAMT)
Curr. (field CUR)

This currency corresponds to:

  • to the site currency if no supplier is entered,
  • to the supplier currency.

The amounts of the purchase request line are expressed in this currency.

SEEINFO It is recommended to use the ISO coding during the creation of a new currency.
field LINACC1

This field indicates the purchase accounting account. The charts of accounts that can be accessed depend on the account core model associated to the company of the movement. If this field is not entered, the account will be automatically determined by the accounting code of the product (according to the setup of the automatic journal PQUIS).
SEEINFO The presence of this field depends on the entry transaction used.

Purchase type (field LINPURTYP)

It is the purchase type (purchase of goods or purchase of fixed assets) used to determine, when it is modified, the account and the tax account to use. The purchase type is initialized by default according to the tax associated to the product account.
field CCE1

The analytical dimensions are initialized in compliance with the Default dimensions setup (PSD dimension code) linked to purchase requests. These dimension codes can be modified manually if authorized by the transaction.

When an analytical dimension type is used for the Project management tracking, then any modification of the project code made at header level will be redistributed to the lines; if the modification applies to a document line, then the dimension code of the dimension type will be reset. This reinitialization is compliant with the Default dimensions setup.
Tax 1 (field VAT1)

This field is used to enter a first tax code to apply.
Only one tax code consistent with the legislation and the group of the site company can be entered.
SEEREFERTTOThe general principles linked to the multi-legislation setup are detailed here.
Tax 2 (field VAT2)
Tax 3 (field VAT3)
Receipt tax (field TAXRCP)
Issue tax (field TAXISS)
Other tax 1 (field TAXOTH1)
Other tax 2 (field TAXOTH2)
Closed (field LINCLEFLG)
Signed (field LINAPPFLG)
Maintenance line id (field PSDNUMMMS)

This field is submitted to the MMS - MMS Interface - X3 activity code.
It is only loaded if the purchase request is coming from an import via the interface with the AXEL - MMS product.
In that case, it contains the identifier of the request line coming from the MMS.

Status

Signature (field XAPPFLG)
Closed (field XCLEFLG)
Ordered (field XORDFLG)
Printed (field XPRNFLG)
Maintenance identifier (field PSHNUMMMS)

This field is submitted to the MMS - MMS Interface - X3 activity code.
It is only loaded if the purchase request is coming from an import via the interface with the AXEL - MMS product.
In that case, it contains the number of the request line coming from the MMS.
field BUTMMSURL

This button is submitted to the MMS - MMS Interface - X3 activity code.
It is used to open the URL that gives access to a web page containing the MMS documents linked with the purchase request.
Budget

Click this action to view the budget on which the purchase request line is posted.

Copy PR Line

This action can only be accessed if:

  • The purchase request has not been closed in its entirety
  • The purchase request is not signed in its entirety
Close a PR Line
Line Text Entry
Base Product Management

Use this action to access the pre-commitments corresponding to the purchase request line.
Price Calculation Window
Approval history
Approval circuit

This action can only be accessed when the signature management is activated (general parameter). Click this action to view the signature stage of the purchase request by displaying for each line:

  • The code of the next signer, which is empty when there are no longer any signatures expected for this document
  • The code for each signer in the circuit as well as the signature date when this signer has already signed.
Purchase journal traceability

Click this action to access the Document traceability inquiry function. This function is used to view and browse through the hierarchy of journals at the origin or coming from the document.
PR line situation display
Product notes

Click this action in order to open a window displaying the note(s) associated with this product.
This information can relate to product availability, additional or substitute products, or a promotional message.
This window could open automatically depending on the setup defined when creating the notes.

Notes are limited to a screen inquiry and cannot be printed.

For further information, see the documentation on Notes.

Reports

By default, the following reports are associated with this function :

  BONDA : Purchase request notes

  PREQUISE : Purchase request list

  PREQUISL : Detail purchase request list

This can be changed using a different setup.

This setup is performed at the Customization level of the current object, by associating a report code or a print code to it.
It is possible to further specify this setup:

  • By specifying a given report at transaction entry level. If this report matches a print code, the list of reports associated with this print code is also submitted.
    The report entered at transaction entry level and the reports associated with the print code are automatically submitted in creation mode only.
  • At a more detailed level, by associating a print template with the BP. This template mentions the report to be used in priority for the printing of each document, as well as the expected number of copies.
    SEEINFOIf the number of copies is not specified, or if there is no print template associated with the BP, the number of copies defined for the Destination printer is chosen. If the number of copies is not specified for the destination printer, then a single copy is printed by default.

Specific Buttons

Order

Click this action to view the order lines created from each line of the purchase request with, for each line, the order number and the order line number, the purchase unit and the quantity.

Close

Click this action to close all the unclosed lines of a purchase request.
In order to avoid closing a purchase request inadvertently, a warning message is displayed to give you the choice to proceed or not.

Click this action to:

  • Enter purchase request header text at any stage of the creation process
  • Modify this text on purchase request modification.

During the transformation of a document, this text is never propagated to the other documents.

Click this action to:

  • Enter purchase request footer text at any stage of the creation process
  • Modify this text on purchase request modification.
During the transformation of a document, this text is never propagated to the other documents.

Clock this action to view the orders associated with the current purchase request.

Click this action to view the purchase request transaction used.

Click this action to access the Document traceability inquiry function. This function is used to view and browse through the hierarchy of journals at the origin or coming from the document.

Local menus

In addition to the generic error messages, the following messages can appear during the entry :

No sequence number counter has been assigned to this document

This message appears when the assignment of sequence number counters for the Purchasing module has not been carried out. To correct this problem, check that the required sequence numbers are available (if this is not the case, they should be created), then assign them to the different documents using the appropriate function.
See the Prerequisites for this documentation.

Setup of the signature rules does not exist for the company

This message appears during the entry of the request site, when the signature management is active and no setup exists for the signature rule for the legal company to which the request site is attached.

XXX Problem when retrieving the sequence number counter

This message appears in creation mode when the reading of the specified sequence number counter is invalid and the system has been unable to get a sequence number.

Manufactured products are prohibited

This message appears when the entered product is part of a category of non-bought manufactured products.

The site is not in the same legal company.

This message appears when the reception site entered does not belong to the same legal company as the request site. To correct this problem, it is necessary to select a site from the suggested list.

Unavailable period from ../.. to ../..

This message appears when the required reception date entered falls in one of the unavailable periods for the receiving site.

The supplier is on hold

This message is displayed when the entered supplier has been specified to be 'on-hold' in the supplier record. This message can be a simple warning message or a blocking message depending on the value given to the dispute code in the supplier record.

The product is not referenced at the supplier's.

This message appears when the requested product is not referenced for the entered supplier. This message can be a simple warning message or a blocking message depending on the value given to the ITMBPS - Supplier referencing parameter (ACH chapter, REF group).

The product is not listed by this supplier for the site.

This message appears when the requested product is not referenced at Product-Sites level for the entered supplier. This message can be a simple warning message or a blocking message depending on the value assigned to the ITMBPSFCY - Supplier-Site referencing parameter (ACH chapter, REF group).

The product is disputed

This message appears when the requested product has been declared as "blocked" in the product record for the entered supplier. This message can be a simple warning message or a blocking message depending on the value given to the Blocking code in the product record (Product-Supplier section).

The entered quantity cannot be less than the consumed quantity

This message appears when the quantity of a generated line is modified after taking into account the requirements, and when the quantity entered is less than the sum of quantities of the requirements that have been taken into account.

Insertion not possible

This message is displayed when an attempt is made to insert a line or duplicate a line when the maximum number of lines for a purchase request, defined by the appropriate activity code, has been reached.

The quantity is null, the line will not be saved

This message is displayed after entering a PR line, when the requested quantity is null: the line is not valid but it is still displayed for potential modification. If the quantity is still equal to zero when the PR is validated, the line will not be kept.

Validation impossible Budget exceeded line ###.

This message appears when the user tries to create a purchase request (or save a modification) while at least one of the lines show a budget overrun and the BUDCNTPRP - Precommitment control type parameter (BUD chapter, CMM group) shows a blocking control. The PR lines remain displayed in order to enable the user to modify the line with a budget overrun or to abort the processing.

No line entered. Update impossible.

This message is displayed on purchase request validation when no line has been entered or when a single line has been entered with a requested quantity equal to zero: the purchase request is not created.

Modification impossible

This message appears when trying to modify a purchase request or when the latter is completed, fully signed or fully ordered.

Closing of the line not authorized

This message appears when trying to close a line that has just been entered but that has not been created yet. To solve this issue, save your purchase request by clicking Create or Save and return to this request in modification mode.

PR line ordered or partly ordered. Modification or Deletion impossible

This message appears when trying to modify or delete a fully or partially ordered PR line.

PR line signed or partly signed. Modification or Deletion impossible.

This message appears when trying to modify or delete a fully or partially signed PR line. To solve this problem, the user needs to cancel the affixed signatures if they have the necessary authorizations.

PR line closed. Modification or Deletion impossible

This message appears when trying to modify or delete a closed PR line. To solve this problem, the closing need to be cancelled, if possible in this context.

Validation impossible At least one line with a null quantity

This message appears when saving a PR modification, and at least one line contains a requested quantity equal to zero: the PR lines are still displayed for a new modification.

Tables used

SEEREFERTTO Refer to documentation Implementation