Exit in VA31 To Prevent Creating of Scheduling Agreement

Hello,
I have looked through the threads and did not fnd my answer, so I am opening this thread. I have a requirement that under certain conditions a scheduling agreement cannot be created for a particular ship-to and/or bill-to. Is there a particular ext that someone have used before to provide this type of functionality?
Regards, Dean.

hi
you may use here form USEREXIT_CHECK_VBAK in program MV45AFZB
to display MESSAGE E...
regards, darek

Similar Messages

VA31 - Create a scheduling agreement

Dear Gurus,
When trying to create a scheduling agreement using VA31, I input the following data:
Sched. Agreemt Type
Sales Organization   2200   France, Paris
Distribution Channel 14     Service
Division             00     Cross-division
Sales Office         2200   Office Paris
Sales Group          2200
Now, I cannot choose any Scheduling agreement type from a drop down menu as none seems to be linked or created for that sales area.
Can anyone help me create a list of Scheduling agreement I can choose from?
Thanks
Chris

Scheduling agreement type should have been created in VOV8 and then this document type should have been assigned to your sales area 2200 / 14 / 00 in OVAZ. Check whether you have assigned your scheduling agreement type in OVAZ.
thanks
G. Lakshmipathi

BAPI for creating sales scheduling agreement

Hi All,
I have a scenario where i need to create a sales scheduling agreement using VA31. I have tried using a function module "SD_SALESDOCUMENT_CREATE". I am able to create the document by inserting the correct data in "SALES_HEADER_IN", "SALES_ITEMS_IN", "SALES_PARTNERS" and using the update flag as " I ".
When I try to insert data in "SALES_SCHEDULES_IN" the function module returns error message "No schedule line category could be determined during quantity adjustment".
please provide help in finding out the right procedure for creating the scheduling agreement with schedule lines data.
Regards.
Anurag

Hi,
Did you shown this to your functional team.
Regards,
Madhu.
Edited by: madhurao123 on Nov 21, 2011 3:29 PM

How are deliveries automatically created from scheduling agreement?

How are deliveries automatically created from the schedule line of the scheduling agreement? Can anybody explain this step by step? Can we use the code VL10BATCH for this purpose? If we can, how is this code used?
Thanks in advance.

hi
A customer scheduling agreement is an outline agreement with the customer containing delivery quantities and dates. These are then entered as schedule lines in a delivery schedule. You can either create schedule lines when you create the scheduling agreement or you can create them later.
You fulfill a scheduling agreement by creating the deliveries in the schedule as they become due. You process deliveries for a scheduling agreement in exactly the same way as you process a normal delivery. After you have carried out the delivery, the system updates the Delivered quantity field in the scheduling agreement item with the delivery quantity.
The scheduling agreement is used as a basis for delivering a material. The customer sends in scheduling agreement releases, referred to as delivery schedules, at regular intervals to release a quantity of the material.
Document Types
To configure document types for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Header -> Define sales document types in Customizing for Sales and Distribution.
The R/3 System contains the following document types for component suppliers:
LZ - Scheduling agreement with delivery schedules (no external agents)
LZM - Scheduling agreement with delivery orders
LK - Scheduling agreement with delivery schedules (external agents)
ED - Delivery by external agent (consignment issue)
EDKO - External agent correction
RZ - Scheduling agreement returns (no external agents)
KAZU - Consignment pick-up for external agents
KRZU - Consignment returns for external agents
Item Categories
To configure item categories for scheduling agreements, choose Sales -> Sales Documents -> Sales Document Item -> Define item categories in Customizing for Sales and Distribution.
The system determines the following item categories for the related document types in
documents containing materials with item category group NORM:
Item category LZN for scheduling agreement type LZ
Item category LZMA for scheduling agreement type LZM
Item category LKN for scheduling agreement type LK
Item category KEN for document type ED
Item category EDK for positive corrections (or the manual alternative EDK1 for
negative corrections) for document type EDKO
Item category REN for document type RZ
Item category KAN for document type KAZU
Item category KRN for document type KRZU
Schedule Line Categories
To configure schedule line categories for scheduling agreements, choose Sales -> Sales Documents -> Schedule lines -> Define or Assign schedule line categories in Customizing for Sales and Distribution.
The R/3 System contains the following schedule line categories for component suppliers:
L1, BN, L2, and CN for item category LZN
E4, E0, E5, and BN for item category LKN
L2 for item category LZMA (standard for delivery order processing)
Schedule Line Types
To configure schedule line types for scheduling agreements, choose Sales -> Sales Documents -> Scheduling Agreements with Delivery Schedules -> Define schedule line types in Customizing for Sales and Distribution.
Creating Scheduling Agreements
To create a scheduling agreement with delivery schedules:
1. In the Sales menu http://Ext. choose Scheduling agreement ->Create.
2. Enter scheduling agreement type LK (standard) or LZ (external agents) and the
relevantorganizational data.
3. Choose ENTER.
4. Enter the following data:
Sold-to or ship-to party number
Purchase order or closing number
Material or customer material number
You can use the Description field to identify the scheduling agreement. For
example,
you could enter the model year for a particular production series.
The system allows up to 35 digits for a customer material number.
Rounding quantity
Usage
Choose Goto -> Header -> Sales to enter the usage at header level, or Goto ->
Item-> Sales A to enter it at item level. The system proposes usage S, for series, as default in both cases.
Planning indicator
Choose Goto -> Header ->Sales.
Target quantity
Mark an item and choose Goto -> Item -> Sales A
Partners
For scheduling agreements with external agents , choose Goto -> Header
->Partners to enter the external agent as forwarding agent and special stock partner
on the partner function screen.
5. Create a delivery schedule
Mark an item in the scheduling agreement and choose Goto -> Item -> <Delivery
schedule>. Enter:
A delivery schedule number and date
The cumulative quantity received by the customer
The last delivery confirmed by the customer
A schedule line with date, time, and quantity
To enter additional data in the delivery schedule, choose DlvSch.Hdr (delivery schedule header).
configuration:
img->SD->Sales->sales document->scheduling agreements with delivery schedules->
step1: define schedule line types
schedule line types are not schedule line categories. Schedule line types are used for information purpose only.
stds are 1. fixed date 2. backlog 3. immediate requirement
4. estimate
step2: maintain planning delivery sched. instruct/splitting rules
The planning delivery schedule is an internal delivery schedule used to plan requirement s more efficiently. It is sub divided into 3 parts
2.1 delivery schedule splitting rules
2.2 dly schedule instrusctions
2.3 assign dly schedule splitting rules
step3: define sales documents type
step4 : define item categories
step5: define schedule line categories
step6: maintain copy control
PROCESS
step1: create scheduling agreement
VA31
enter SP,SH valid from, valid to,
goto ITEM OVERVIEW tab
enter material, rouding qty
select ITEM click on FORECAST DLSCH
enter different dly dates and qties
save it.
step2: create sales order with reference to above
step3: create delivery
step4: create billing
regards
krishna

Error in creating a schedule agreement

hi friends
i got an error in creating a scheduling agreement
the error reads- 'zjk5(the output type ) is not defined'
condition records,port definition,partner profiles everything is fine.
another error that reads is 'No communication data is set for medium 6ie edi'
please answer this problem.thanks is advance.

Hi,
Check the Output type was created or not for that Scheduling Afreement?
check the table T685 for that Output type?
And n the diocument have you configured the Output type with the correct medium (EDI value 6) and have you assigned the same in NACE tcode?
check
reward points if useful
regards,
Anji

Funktion to create MM Scheduling agreement

Dear all,
I am looking for a funktion/bapi to create material scheduling agreements in SAP. I think BAPI_PO_CREATE1 does only create purchase orders. Any ideas how to create scheduling agreements by funktion?
Kind regards
Roman

Hi,
Did you read the FM documentation.
there a table parameter for Schedule lines.
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Check it...
you can use it to create the schedule lines also...
Regards
vijay

I have created a scheduling agreement for a material i want to cancel.

i have created a scheduling agreement with a material i want to use the material in a contract with another vendor, is there any way i could use the material or i have to terminate the scheduling agreement and create the contract. in case of canceling the agreement what are the steps involved i mean the T Codes.

Hi,
First af all you have not mention that is ther any subsequent delivery documents are exist against that scheduling agreement or not....if yes then you cannot delete the scheduling agreement unless u reverse the deliveryin t-code VL09 and by cancelling billing docs in VF11(if invoice created) as well...
If thr is no Deliveries, then you can delete that scheduling agreemnt very well, by going VA32 enter agreement no., press enter
on top selct sales doc option and delete the agreeement...
Reg
JJ
Edited by: Jagsap on Jul 9, 2009 2:11 PM

Is it possible to create Automatic Scheduled Agreement like Automatic PO

Could you please explain, is it possible to create an automatic schedule agreement from the PR, PIR (ie.e viz.. as Creation of Automatic Purchase Order)

Hi
Why you want to generate the Scheduling agreement automatically? What is the requirment? Volume is high?
As Sridhar mentioned you have no option in standard SAP to create automatic scheduling agreement. But you can create delivery schdule via MRP.
If you have more volume then go for developing the program with ABAP guys.
if the requirment is for Cut over only then go for LSMW or BDC options.
Hoe it helps
Karthik

Generate Source List while creating Contract/Scheduling Agreement

Hi,
My requirement is that the Source List for the particular Material / Vendor should be created automatically when I am creating a new Contract / Scheduling Agreement.
How can this be acheived.
Thanks in Advance,
Manju.

Create an LSMW so that while loading contract itself you can also load source list.
Regards
Mohan

BAPI to create Scheduling Agreement of VA31

Dear gurus,
I need to find the BAPI or Function Module to create Scheduling Agreement of VA31 from the uploaded data. I know that I can use BAPI_SALESORDER_CREATEFROMDAT2 to create the sales order of VA01. Can I use the same bapi to create the scheduling agreement of VA31? Both of the screens seems to look quite the same but their order types are different. Any suggestion on this?
Thank you for your help. Have a nice day.
Best Regards,
Hedy

Hi,
FM
BAPI_CUSTSCHEDULAGREE_CONFDELV
Functionality
You can use this method to make a delivery confirmation in the SD scheduling agreement
Example
1. Generating delivery for a scheduling agreement item.
2. Changing a delivery item.
3. Posting of goods issue for delivery.
4. Deleting a delivery item or a delivery.
Regards,
Venkatesh

LSMW - create Scheduling Agreement for subcontracting position type

Hi all,
I want to use LSMW to create a scheduling agreement with position type L (subcontracting).
I'm using Business Object Method BAPI with
Business Object      BUS2013
Method               CREATE
Message Type         PURSAG_CREATE
Basic Type           PURSAG_CREATE01
The LSMW creates the scheduling agreement with the list of material I inserted in my file but with position type 'blank'.
any ideas?
i read that the standard program RM06EEI0 don't support subcontracting, this is the reason of BAPI.
thanks, MG

Hi gurus!
I forgot to put 'X' in E1BPMEOUTITEMX-ITEM_CAT so, even if i mapped the field, it was not updated.
thanks a lot.
problem solved.
MG

How to create correction delivery in schedule agreement

Hi all -
I am loading legacy data into SAP and am creating schedule agreements. I create the agreement using SD_SALESDOCUMENT_CREATE, then COMMIT, then update the schedule lines using BAPI_SALES_DEL_SCHEDULE_CREATE also followed by a COMMIT. This works, and creates the schedule agreement with schedule lines.
At this same time, or even in another BAPI or function call if need be, I need to create a CORRECTION DELIVERY for this schedule agreement. I am populating the CORR_***_QTY_IN and CORR_***_QTY_INX in BAPI_SALES_DEL_SCHEDULE_CREATE with values in every field, and the return tells me 'CORR_CUMQTY_IN has been processed successfully', but when I look at the schedule agreement in VA32, there is no ***. issued qty or ***. delv qty, and no correction delivery has been created.
What am I missing??
Thanks so much...
Sharon

Hi Shyam -
I am calling the BAPI_TRANSACTION_COMMIT function right after the BAPI_SALES_DEL_SCHEDULE_CREATE function. When I call that create function, I am adding schedule lines, so my return table has all of the other successful messages you would expect -
ORDER_HEADER_IN has been processed successfully
CORR_CUMQTY_IN has been processed successfully
DEL_SCHEDULE_IN has been processed successfully
SCHEDULE_IN has been processed successfully
Sched. Agr. w/ Rel. 1030000058 has been saved.
It even says the corrective *** qty was successful....but when I open the schedule agreement, and go to the Forecast Delivery Schedule tab on the line item, the Cml. iss. qty and Cml. dlv. qty fields are blank, and there are no deliveries associated with the order.
Do I have to use a seperate BAPI to create the correction delivery? I've looked at BAPI_OUTB_DELIVERY_CREATE_SLS, but I don't see how to specify that this is a correction delivery and not a 'regular' delivery.
Thanks,
Sharon

Regarding user exit for me32l - Scheduling agreement

hi,
i am using the exit ZXM06U44 for both purchase order and scheduling agreement, but the thing is for purchase order the function module EXIT_SAPMM06E_006 is been triggerin for exproting and importing of the memory if of transaction type, know i need to find out the same thing for scheduling agreement , help me out in this plz.

Check the user exit avilable for transaction ME31 and try to user the user exit which suit your requirement.
I am sending you the list of the enhancements available for ME31.
MEQUERY1
MM06E011
LMEKO001
LMEKO002
AMPL0001
LMEDR001
LMELA002
LMELA010
LMEQR001
LMEXF001
LWSUS001
M06B0001
M06B0002
M06B0003
M06B0004
M06B0005
M06E0004
M06E0005
ME590001
MEETA001
MEFLD004
MELAB001
MEVME001
MM06E001
MM06E003
MM06E004
MM06E005
MM06E007
MM06E008
MM06E009
MM06E010
MMAL0001
MMAL0002
MMAL0003
MMAL0004
MMDA0001
MMFAB001
MRFLB001
Let me know if it works.
Amandeep

User Exit in the Sales order create BAPI

Hi,
Can some one help me in telling if there exists a user exit for the BAPI '/AFS/BAPI_SALESORDER_CREATE'.
This is urgent. So, pls. throw some light on this.
Thanks in advance.

Hi
User Exits In Sales Document Processing
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
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".
MV45AFZZ and MV45EFZ1
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.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
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:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
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.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
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.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD 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_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
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
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.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
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.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
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.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
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).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
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:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
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.
User-Exits for first data transfer:
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)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
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.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
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:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
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.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.

How to know if a schedulling agreement is created via EDI

Hello,
I would like to konw if a schedulling agreement has been created via edi. Is there any field or any transaction where is indicated so?
Thanks a lot!
Regards,
JMadariaga

Hi,
in your title bar "Display scheduling agreement xxxxx", you should have a "Services for Object" icon
If this is not present, you may have to add it to your profile in SU01
(Just set SD_SWU_ACTIVE to X)
If the icon is there, click it
now a small toolbar should appear
If the "display relationships" icon is not greyed out, click it
You should now see all the idocs associated with this scheduling agreement
Hopefully, the first one is the idoc which created the scheduling agreement.
Also, if you just wish to see the last idoc associated with the scheduling agreement
.After you click the Fore Dl Sch tab or the JIT DlSh tab
Click the Dlv Sch Hdr
Then Click the "Curr Idoc" and you will see your current idoc.
kind regards
Paul Quinn

Exit in VA31 To Prevent Creating of Scheduling Agreement

Similar Messages

Maybe you are looking for