You are on page 1of 3

SAP Note

696362 - Exit: Availability control for valuated goods receipts


Version 26 Validity: 02.10.2014 - active

Language English

Header Data
Released On 02.10.2014 11:44:14
Release Status Released for Customer
Component
CO-OM-OPA-C Budgeting
Priority
Recommendations / Additional Info
Category
Consulting

Symptom
When you post a goods receipt or a service entry, no availability control is executed.
Budget overruns may occur as a result.

Other Terms
MIGOMIGO_GRMIGO_GSMB01MB31ML81ML81NML85QA11VI01VI02
ME21ME21NME22ME22NME23ME23NVL31VL31NVL32VL32N
WE12 WE14 WE15 WE16 WE17 WE18 WE19
BAPI_GOODSMVT_CREATEBAPI_ENTRYSHEET_CREATE
No availability control.
Availability check warning error message

Reason and Prerequisites


This is due to the system design - see Note 46209.

Solution
If required, you can also execute an availability control for goods receipts or service entries that
are posted using transactions MIGO, MIGO_GR, MIGO_GS, MB01, MB31, ML81, ML81N, ML85, QA11, VI01,
VI02, VL31, VL31N, VL32 or VL32N or using the follow-on functions ME21, ME21N, ME22, ME22N, ME23 or
ME23N.
For Releases 4.6B, 4.6C, and 4.70, implement the corrections relevant for your release from Note
696361, if they are not already implemented in your system.
Then proceed as follows, depending on your release:
Releases 4.6B and 4.6C
Create utility program ZAIMGRAC with the attribute
Type = S / Subroutine pool
in a customer-specific development class. You can find the source code of the utility program
ZAIMGRAC in the attached correction instruction number 286751.
Releases as of 4.70
The function is implemented using a Business Add-In (BAdI).
1. First, determine whether implementations already exist for the definition name IM_BEHAVIOUR.
For example, you can do this using transaction SE84 (Repository Information System):
a) Select "Enhancements -> Business Add Ins -> Implementations"
b) Select "Classic BAdIs" (only for Release 6.00 and higher)
c) Choose "All Selections" (only for Release 6.00 and higher)
d) Search for the (BAdI) definition name = IM_BEHAVIOUR
2. If no implementation exists, create one using transaction SE19:
a) For Releases 4.70 and 5.00: Implementation for the definition name IM_BEHAVIOUR,
b) For Release 6.00 and higher: Implementation for the classic BAdI with the BAdI name
IM_BEHAVIOUR.
3. Now use transaction SE19 to go to the details of the implementation. Choose the 'Interface'
tab and double-click the method GET_BEHAVIOUR.

4. Add the source code specified in correction instruction number 286755 directly before the
statement ENDMETHOD.
5. Activate the source code corrections.
6. Use F3 to go back and activate the implementation.
Goods Receipt/Service Entry Using BAPI
If you also want the checks for the availability control to be executed for goods receipts or
service entries that are posted using a BAPI, proceed as follows:
l

If the BAPI is called via Remote Function Call (RFC), the pseudo transaction name BAPI_RFC must
be added to the list of transaction names in the user exit (utility program ZAIMGRAC or BAdI
method GET_BEHAVIOUR) - see the relevant line in the source code that has been turned into a
comment.
This is particularly relevant for goods receipts or service entries that are triggered from the
SRM system.

If the BAPI is called directly, the pseudo transaction name BAPI_DIR must be added to the list
of transaction names in the user exit (utility program ZAIMGRAC or BAdI method GET_BEHAVIOUR) see the relevant line in the source code that has been turned into a comment.
This is particularly relevant for calls of the BAPI from customer-specific programs.

Validity
Software Component From Rel.
SAP_APPL
46B
46C
470
500
600
602
603
604
605
606
616
SAP_FIN
617
700
618
720

To Rel. And Subsequent


46B

46C

470

500

600

602

603

604

605

606

616

617

700

618

720

Correction Instructions
Correction Instructions

Software Component
SAP_FIN
SAP_APPL
SAP_APPL

Valid from
617
46B
470

Valid to
720
46C
616

Number
1779649
286751
286755

References
This document refers to:
SAP Notes
1711340 Availability control: Goods receipt/service entry using BAPI
1636093 Avail. control for valuated goods receipts / service entries
1424698 Budget overrun despite active availability control
910472 Exit: Availability control for valuated goods receipt using MIGO_xx
696361 Exit: Availability control for valuated goods receipts
447102 Av. control messages for goods movements/service entries
417169 MIGO: No warning messages when posting goods movement
46209 No availability control for goods receipts

This document is referenced by:

SAP Notes (7)


46209 No availability control for goods receipts
417169 MIGO: No warning messages when posting goods movement
447102 Av. control messages for goods movements/service entries
696361 Exit: Availability control for valuated goods receipts
1711340 Availability control: Goods receipt/service entry using BAPI
1424698 Budget overrun despite active availability control
910472 Exit: Availability control for valuated goods receipt using MIGO_xx