Beruflich Dokumente
Kultur Dokumente
Contents
Making Manual Entry for a Condition-type Possible for Selected Users in Sales order .... 2
User Exits for Transportation.............................................................................................. 3
User Exits for Price Determination ..................................................................................... 3
User Exits for Partner Determination ................................................................................. 7
User Exits For Credit Checks ............................................................................................. 8
User Exit for Availability Check ........................................................................................ 8
User Exit for Risk Management for Receivables ............................................................... 8
User Exits for Billing Plan .................................................................................................. 9
Additional User Exits in Billing Document ...................................................................... 10
User Exits For Product Allocation Processing.................................................................. 10
User Exits For Component Supply Processing ................................................................. 11
User Exits For Product Selection ...................................................................................... 13
User Exits For Resource-Related Billing .......................................................................... 13
User Exits For General Billing Interface .......................................................................... 15
User Exits For Sales Support ............................................................................................ 15
User Exits For Lists .......................................................................................................... 16
User Exits for Payment Cards ........................................................................................... 16
Sales related exits.............................................................................................................. 16
Billing related exits ........................................................................................................... 17
Delivery related exits ........................................................................................................ 18
User Exits In Sales Document Processing ........................................................................ 19
User exits in the screens .................................................................................................... 27
User Exits in Program MV45AFZ4 .................................................................................. 28
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs .................................... 28
New Fields For Free Goods Determination ...................................................................... 28
User exits for Billing ......................................................................................................... 29
Transferring new SD fields to Accounting ....................................................................... 30
User exits for Transportation ............................................................................................ 32
User exits for billing plan ................................................................................................. 34
Some Question Answers ................................................................................................... 35
@sdn.sap.com
No Limitations
2.
A : Free
3.
4.
5.
Selecting any one of this option makes the condition type uniform across all document type and
for users. Often the requirements are like for a group of users the condition type should behave
like C option, for another group like D or for a specific document type it should be A and for others
D.
One of the easiest way to achieve this is through the user-exit
USEREXIT_PRICING_PREPARE_TKOMP in the include MV45AFZZ.
The following code will make the condition type PR00 modifiable for user ABAP1 and nonmodifiable for all other users.
---FORM USEREXIT_PRICING_PREPARE_TKOMP.
DATA : i_T685A TYPE STANDARD TABLE OF T685A WITH HEADER LINE.
IF SY-UNAME = 'ABAP1'.
LOOP AT XKOMV.
IF XKOMV-KSCHL = 'PR00'.
SELECT * FROM T685A INTO TABLE I_T685A WHERE KSCHL = 'PR00'.
READ TABLE I_T685A WITH KEY KSCHL = XKOMV-KSCHL.
I_T685A-KMANU = 'C'.
MODIFY I_T685A INDEX SY-TABIX.
MODIFY T685A FROM TABLE I_T685A.
REFRESH I_T685A.
ENDIF.
ENDLOOP.
ELSE.
LOOP AT XKOMV.
IF XKOMV-KSCHL = 'PR00'.
@sdn.sap.com
Description
Module
Include
Description
@sdn.sap.com
SAPLV60A
RV60AFZZ
USEREXIT_PRICING_PREPARE_TKOMP
SAPLV60A
RV60AFZZ
USEREXIT_FIELD_MODIFICATION
SAPMV61A
MV61AFZA
@sdn.sap.com
SAPMV61A
MV61AFZB
USEREXIT_FIELD_MODIFIC_KOPF
SAPMV61A
MV61AFZB
USEREXIT_FIELD_MODIFIC_LEER
SAPMV61A
MV61AFZB
USEREXIT_PRICING_CHECK
SAPMV61
MV61AFZA
USEREXIT_PRICING_RULE
SAPLV61A
RV61AFZA
@sdn.sap.com
SAPMV61A
MV61AFZA
USEREXIT_XKOMV_BEWERTEN_INIT
SAPLV61A
RV61AFZB
USEREXIT_XKOMV_BEWERTEN_END
SAPLV61A
RV61AFZB
USEREXIT_XKOMV_ERGAENZEN
SAPLV61A
RV61AFZB
USEREXIT_XKOMV_ERGAENZEN_MANU
SAPLV61A
RV61AFZB
USEREXIT_XKOMV_FUELLEN
SAPLV61A
RV61AFZB
@sdn.sap.com
SAPLV61A
RV61AFZB
USEREXIT_PRICING_COPY
SAPLV61A
RV61AFZA
Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been
converted from a full screen to a subscreen. The full screen is included in the
SAPMV61A module pool, the subscreen, however, in program SAPLV69A. Therefore,
instead of MV61AFZA and MV61AFZB, the user exits in LV69AFZZ should be used. For
reference, see OSS note 313569.
You can use this user exit to control whether an address that was entered
manually and has already been used in other documents (referenced), should be
referenced again if it changes or whether a new address shold be created
(duplicated).
EXIT_SAPLV09A_002
Call up this user exit if a customer has not been maintained in the current sales
Posted By: Sudipta Sanyal on August 2009
Page: 7
@sdn.sap.com
Use this user exit to control the origin of partners in the partner determination
procedure (origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this
user exit is automatically called up during partner determination.
EXIT_SAPLV09A_004
Use this user exit to integrate your own check in a program, that runs before the
partner is saved in the document.
For more detailed information, see the program documentation for each ofthe
user exits.
@sdn.sap.com
BILLING_SCHEDULE_DELTA
For milestone billing a percentage value is fully invoiced for each
billing deadline. In the case of deviations between the original
item value and any later changes, you can use the user exit to
determine whether the difference should be stored in the final
invoice or sent to the next deadline.
USEREXIT_MOVE_FIELD_TO_FPLT: This user exit
allows you to create your own fields in table FPLT.
USEREXIT_MOVE_FIELD_TO_FPLA : This user exit
allows you to create your own fields in table FPLA.
RV60FUS2
USEREXIT_PRICING_PREPARE_TKOMX
This user exit is used to copy or create an additional field in the
definitive communication structure for pricing.
The user exit is also often used to change the duration of a
billing plan deadline. You can do this by overwriting the following
fields:
tkomp-anz_tage (Number of days in a
deadline)
tkomp-anz_monate (Number of months in a
deadline)
tkomp-anz_jahre (Number of years in a
deadline)
tkomp-anz_wochen (Number of weeks in a
deadline)
RV60FUS3
USEREXIT_DATE_PROPOSAL
In the standard release deadlines are set according to a template
in the billing plan. This grid entry list sets the deadlines for each
day but you can adjust the template with the user exit so that the
grid entry list could, for example, follow a monthly pattern
instead.
Modification report for billing plan SDFPLA02
This report enables you to update the header data for a billing
plan with the result that new billing plan deadlines are
determined and set in the billing plan.
In this way you can, for example, set the goods issue date as the
starting date for the billing plan.
Additions to billing plan with transaction SMOD
User exit SDVAX001
In the standard release the billing plan type is determined from
the item category of the sales document and set in the billing
plan.
You can also use the user exit to determine the billing plan type
dependent on data from the order header, order item, etc.
User exit V60F0001
This user exit is for changing the deviating billing date (FPLT-
@sdn.sap.com
RV60FUS5
This userexit
can be used to
split date lines
TKOMK for
Header fields
RV60FUST
SDQUX0001 Function module exit for enhanced check in SD product allocation User
USEREXIT_ADD_FIELD_TO_HEADER
USEREXIT_ADD_FIELD_TO_LINE
USEREXIT_DELIVERY_GROUPS
USEREXIT_MVERF_INIT
USEREXIT_QUOTA_KEY_VALUE
USEREXIT_AVAILABILITY_IN
@sdn.sap.com
USEREXIT_AVAILABILITY_OUT
USEREXIT_DARA_REFRESH
USEREXIT_PLANT_SELECTION
This user exit is used to adjust the flow during plant transfer. A list of permitted plants, where this
material is created, is determined and checked in the standard R/3 delivery. A dialog box appears
where you can select the plants. The user exits allow you to modify the plant table so that plant
selection takes place in advance for every flagged selection and a dialog box becomes
unnecessary.
USEREXIT_CHECK_VBLB-USR01
USEREXIT_CHECK_VBLB-USR02
USEREXIT_CHECK_VBLB-USR03
USEREXIT_CHECK_VBLB-USR04
USEREXIT_CHECK_VBLB-USR05
General
EXIT_SAPLVED4_004
You can use this user exit to overwrite the standard method with which the system determines
the recipient of messages (either at sales document level or in the customer master record). You
can define a special recipient for an incoming document that has just been processed.
EXIT_SAPLV45L_002
With this user exit, you can change the VBLB structure (sales document: delivery schedule data),
before the system copies delivery schedule data to the corresponding internal table.
@sdn.sap.com
EXIT_SAPMV45L_002
This user exit allows you to modify the calendar used in a delivery schedule split.
For workflow
EXIT_SAPLVED4_001
EXIT_SAPLVED4_002
EXIT_SAPLVED4_003
EXIT_SAPLVED4_005
EXIT_SAPLVED4_006
These user exits allow you to change the workflow parameters for processing inbound EDI
messages.
EXIT_SAPLVED4_001
EXIT_SAPLVED4_005
EXIT_SAPLVED4_006
You can use these user exits for the standard self-billing procedure.
EXIT_SAPLVED5_002
EXIT_SAPLVED5_003
EXIT_SAPLVED5_004
You can use these user exits for the self-billing procedure with invoice creation.
@sdn.sap.com
V45A0001 Function module exit for developing alternative materials for product
selection{*}
RV45HFZZ enhancement
USEREXIT_INV_REQ_ITEM
USEREXIT_INV_REQ_ITEM_PARTNER
You can use the following user exits for resource-related billing as of Release 4.5A:
V46H0001 enhancement
EXIT_SAPLV46H_001
EXIT_SAPLV46H_002User Exits For Billing
@sdn.sap.com
USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function
group V60B):
@sdn.sap.com
MCV2001 - Expand LIS fields for sales activities/sales promotions. This enhancement
contains the following user exit:
EXIT_SAPLMCV2_001
V43MLIS - Expand LIS fields for address lists. This enhancement contains the following
user exit:
EXIT_SAPLV43M_007
V43K0001 - Enhancement for linking to calendar. This enhancement contains the
following user exit:
EXIT_SAPLV43K_001
V43ADATA - Change sales activity data in dialog. This enhancement contains the
following user exit:
EXIT_SAPMV43A_007
@sdn.sap.com
This allows the list structure of individual fields to be filled on header and item
levels.
RVKPRFZ2
This allows the sort sequence for the first issue of the list to be defined.
RVKPRFZ1
RVKPRFZ1
There are two additional user exits for listing sales documents, which influence the way in which
the communication structure is filled. These user exits do not affect the structure of the list but the
way in which the data is transferred and how the new additional fields are filled.
CUSTOMER_FILL_1
CUSTOMER_FILL_2
Description
SDAPO001
SDTRM001
V45A0001
V45A0002
V45A0003
V45A0004
V45E0001
V45E0002
@sdn.sap.com
V45P0001
V45S0001
V45S0003
V45S0004
V45W0001
V46H0001
V60F0001
Description
MV45ATZZ
MV45AOZZ
MV45AIZZ
MV45AFZZ and
MV45EFZ1
For entering installation-specific FORM routines and for using user exits,
which may be required and can be used if necessary.
Description
SDVFX001
SDVFX002
SDVFX003
SDVFX004
SDVFX005
SDVFX006
@sdn.sap.com
SDVFX008
SDVFX009
SDVFX010
SDVFX011
V05I0001
V05N0001
V60A0001
V60P0001
V61A0001
Description
V50PSTAT
V50Q0001
V50R0001
V50R0002
V50R0004
V50S0001
V53C0001
V53C0002
V53W0001
@sdn.sap.com
VMDE0002
VMDE0003
VMDE0004
V02V0001
V02V0002
V02V0003
V02V0004
Description
MV50AFZ1
MV50AFZ2
MV50AFZ3
MV50AFZK
The user exits in this include can be used to fill the condition tables for material
listing and material exclusion (KOMKG and KOMPG) and product selection
(KOMKD and KOMPD) with own data.
MV50AFZL
In delivery creation process for sales orders there is the possibility to restrict the
delivery creation to some order items. If these order items are member of a delivery
group, but not all items of this delivery group are includes in the restriction range of
the order item nubers, you can specify in this routine what to do.
MV50AFZP
This user exit can be used to modify change mode of pricing screens in delivery
processing.
MV50AFZZ
@sdn.sap.com
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with
"ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are
called up by the screen and run under PBO (Process Before Output) prior to output of the screen.
The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are
called up by the screen and run under PAI (Process After Input) after data input (for example,
data validation). The modules must start with "ZZ".
For entering installation-specific FORM routines and for using user exits, which may be required
and can be used if necessary. These program components are called up by the modules in
MV45AOZZ or MV45AIZZ.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales
document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during
order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the
routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited
together during a modification in ABAP. If a field has no field name, it cannot be allocated to a
group.
The usage of the field groups (modification group 1-4) is as follows:
@sdn.sap.com
Modification group 3: For modifications which depend on check tables or on other fixed
information
The FORM routine is called up for every field of a screen. If you require changes to be made, you
must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in
the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in
the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is
described in the section "Copy customer master fields into sales document" .
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment
depending on the required fields. For example, if you want to define the number range depending
on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the
communication structure KOMK taken as a basis for pricing.
@sdn.sap.com
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this
indicator at the beginning of the safety routine. This is why this indicator must also be set during
the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is
the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication
structure KOMPD taken as a basis for the material determination. This is described in detail in the
section "New fields for material determination ".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure
KOMKG taken as a basis for material determination and material listing. This is described in
detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
@sdn.sap.com
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales
document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each
case it must be reset again before processing the next document so that the credit limit is not
used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document
with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are
met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document
header. The system could, for example, check whether certain shipping conditions are allowed for
a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business
data in the order.
@sdn.sap.com
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial
number.
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can
include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can
include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to
display a certain field in the account assignment block (see also MV45AFZB).
@sdn.sap.com
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard
system, the delivering plant is copied from the customer master or the customer-material info
record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure
SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will
find notes on the user exit in MV45AFZB.
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the
sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a
sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a
sales document schedule line)
@sdn.sap.com
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record
(e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain
item field could be used as the precondition for pricing to be carried out again). Further
information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer
group or price group could be set as the preconditions for the system to carry out pricing again).
Further information in MV45AFZB.
@sdn.sap.com
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item
status).
The following workareas are available for this user exit:
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
@sdn.sap.com
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure
KOMP for free goods determination. For more information see the New Fields for Free Goods
Determination IMG activity.
The following communication structures are relevant for free goods determination:
For technical reasons, communications structure KOMG is used to display the totals from KOMK
and KOMP. It contains all the fields that can be used for the material determination. If new fields
are added to KOMK or KOMP, they are automatically added to KOMG.
New fields for free goods determination are added in the following INCLUDES:
The routines for adding new fields in sales order processing can be found in Member
MV45AFZ4. Use the following user exits:
@sdn.sap.com
An example of a statement for adding new header fields to free goods determination could be:
FORM USEREXIT_MOVE_FIELD_TO_KOMK.
MOVE VBAK-FFELDXY TO KOMK-ZZFELDXY.
ENDFORM.
@sdn.sap.com
USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
USEREXIT_INV_REQ_ITEM
USEREXIT_INV_REQ_ITEM_PARTNER
SDVFX001 Transfer header line (module pool SAPLV60B, programs LV60BU01 and
LV60BU02)
This user exit allows you to carry out changes in the header information line XACCHD or
in the item information line XACCIT for subsequent billing documents in accounting.
SDVFX002 Transfer customer line item (module pool SAPLV60B, program LV60BF00)
This user exit allows you to carry out changes to the item information line XACCIT for
subsequent billing documents in accounting. The customer line can also be changed.
@sdn.sap.com
SDVFX004 Transfer G/L account line (module pool SAPLV60B, program LV60BF00)
This user exit allows you to carry out changes to the item information line XACCIT for
subsequent billing documents in accounting.
Note
As an alternative you can still use the user exits that were available before Release 3.0 in
INCLUDE RV60BFZA.
o
USEREXIT_FILL_XKOMK1
USEREXIT_FILL_XKOMK2
USEREXIT_FILL_XKOMK3
USEREXIT_FILL_XKOMK3_ACCR
USEREXIT_FILL_XKOMK3_CASH
@sdn.sap.com
INCLUDE MV56AIZZ
You can include your own modules in this program, to be processed in shipment processing
screens during PAI.
INCLUDE MV56AFZY
You can include your own FORM routines in this program. They can contain your own
adjustments for shipment processsing.
INCLUDE MV56AFZZ
This program contains pre-defined FORM routines, in which you can carry out your own
adjustments for transportation processing.
USEREXIT_FIELD_MODIFICATION
You can use this routine to modify the attributes in screen fields. This routine is called up by the
routine FELD_AUSWAHL.
The following enhancements (transaction CMOD) are available for transportation (you will find
more specific information about the individual user exits in transaction CMOD as documentation
to the respective enhancements or as documentation of the relevant customer functions).
This function is used for including user-defined activities that must take place once a
status has been set in the shipment header.
@sdn.sap.com
@sdn.sap.com
USEREXIT_MOVE_FIELD_TO_FPLT
This user exit allows you to create your own fields in table FPLT.
USEREXIT_MOVE_FIELD_TO_FPLA
This user exit allows you to create your own fields in table FPLA.
@sdn.sap.com
@sdn.sap.com
Question 2: Why the sales order is not blocked although I get the information message saying
"*** credit check: credit limit exceeded"?
Answer: Please check the setting in T-code OVA8.
Field "Reaction" and "Status/Block" must be set together.
If not, the sales order won't be blocked even when the credit check failed.
Question 4: I have set all the settings for credit check; however the credit value is not updated
correctly, why?
The credit check and the update of the credit values are separate
processes which are also controlled separately by the respective
customizing:
1) credit check is controlled by transactions OVAK and OVA8. Relevant note 18613
2) update of the credit values is controlled by VOV7 or OVA7: "credit acttive" flag. The 'Credit
active' setting only affects the credit
update of the SD credit values (open orders, open delivery and open billing documents). This flag
has no control on the credit check. So
if for an order type, there is no credit check in OVAK and OVA8 but the "credit active" flag is set
for the item category, the order will
update the credit values even if no credit check is performed for the order.
If the flag "credit active" is not set, the system will not update the open credit values. On the other
hand, the system ALWAYS updates the FI
credit value 'Open receivable' when the billing document is transferred to Accounting. So,
although you deactivated the "Credit active" flag in
in OVA7 or VOV7, such an item will increase the 'Open receivables' and thus the credit limit used
when the corresponding billing document is
posted to Accounting.
@sdn.sap.com