Screen Exit in Sales Order
Hi All,
I have added three fields in Additional tab 'B' in the Header level of Sales Order (VA01) Transaction screen exit (SAPMV45A - Screen no: 8309). But my problem is i am unable to see the fields in the header level of VA01 transaction after activating the screen. Please suggest me how to display the fields in the header level of VA01 Tcode.
Thanks,
Santosh
Hi Santosh,
We usually do assign a User exit to a Project & activate.
Just follow the nice link on Wiki for User exit assigning to a project.
[Customer Exits (CMOD) |http://wiki.sdn.sap.com/wiki/display/ABAP/CustomerExits%28CMOD%29]
Regards
Abhii
Similar Messages
-
Is the Screen Exit for SALES Order
Hi,
I want to add Two Fields in the SALES ORDER. Can any tell me exit for to add new fields in VA01.
Thanks
Regards
PrashanthYou cau use the screens used in the tabs (header and item): additional data B.
In these tab screens exit are called, in these screen you can insert your fields.
The screen are:
SAPMV45A8309, Sales Document Header - User Exit Header
SAPMV45A8459, Sales doc. Item - User exit item
Use screen painter to change them. (transaction SE51) -
I want to add an field in additional data B screen of VA03 .
Pls help with some screen exit.Hi Shivram,
you can add your field in Sales Order Screen Additional Tab B (Program:SAPMV45A and Screen No:8309)
and Following user-exits could be used for validating the field and modify field content:
 MV45AOZZ User-modules PBO (Process Before Output)
 MV45AIZZ User-modules PAI (Process After Input)
 MV45ATZZ Data Definitions
 MV45AFZZ Subroutines
Thanks and Regards,
pavankumar -
Need to create screen exit for Sales Order Transaction
Hi all,
I need to show some additional data on 'ADDITIONAL DATA B' tab of the sales order transaction... I have created a project but not able to get the enhancements that are to be used...
Will be really very heplful if you let me know, which one to use also why to use it...and how to determine which enhancement is to be used.... As i am new to User Exits...Hi ,
Check out this exits.
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0001 Determine alternative materials for product selection
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
SDAPO001 Activating Sourcing Subitem Quantity Propagation
Check some of badi .
Please reward if useful. -
What are the User Exits for Sales Order creation process?
Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
MindaugasPlease check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
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.
Regards
Eswar -
Screen variant for sales order screen
Hi,
I have a problem in using screen variant in sales order screen.
I want to make gray the columns of material , material quantity in sales order screen but when I use screen variant and check the output only for these columns , it does not work ( I provided these in delivery document and it work)
I want to know that is it possible to make gray for material and material quantity column with screen variant or I can use another way?
Thanks.
LidaHi Lida
If I am getting it correctly,
When an end user enters any particular sales order ,u dont want user be able to add additional line item into the already created document,Right?
Now there are 2 possibilities here ,
1.If order or line item has status completed then u want to block?
2.Order is in incomplete state inspite that u want to block.
System does not stop addition of line item in already created even completely processed sales order.
You can do this by enhancing code in PBO module.You need to take help of ABAP developer for this.
We have used order and lne item status in vbuk table for this .
Create a custom error message for validation.
U can use exit MV45AFZZ for the same.
Hope this helps
Regards
Mandar -
Dear All,
I want to control the update pricing button in the condition tab screen of the sales order.
I want to control for the same to be given to only specific users.
Can anybody help me with the detailed steps for doing the same.
Awaiting an early reply.
Regards
AnshIf the user id is different, then your basis people can do this
On the other hand, if multiple users from different places accessing the same user id and you want to control, then you can try with sale order user exit USEREXIT_MOVE_FIELD_TO_VBAP or USEREXIT_CHECK_VBAP in MV45AFZZ where you need to define some logic
thanks
G. Lakshmipathi -
Hello All,
I am working on ECC 6.00 SD module
I want to add partner function in the main screen of the sales order, that mean add more partner function beside Sold to party and the ship to party to be in the order header, Is it possible and how?
Regards
Jacopo FrançoiseHi
If you want in the sales order , above the sold to party as the box then you need to go for enhancements
Regards
Srinath
Edited by: sri nath on Jun 11, 2008 6:56 PM -
Hello All,
Is it possible to define screen layout of sales orders VA01/VA02? The requirement is to disallow changes in the unit of measure field when creating or changing an SO.
In IMG > MM > Purchasing > theres Define screen layout at document level. Is there a similar functionality in SD?
Suggestions for possible work arounds are welcome also.
Thanks!Hello All,
Thanks for your input.
SHD0: Should this creation of a transaction variant a BASIS Security task?
VOV8: Do i place the variant in Transaction Flow > Variant Field? -
User exit on Sale order creation - Prog- SAPMV45A, Screen - 8459
Hi All,
I have added additional fields on Additional data tab on sales order creation screen on screen no 8459.
I have decleared the fields in PAI as well as defined all of them in layout.
But out of 14 fields only 13 input fields gets displayed on screen.
The height and width of screen are enough to display all fields.
Is there any limitation on maximum no of fields can be defined on screen?
How can i resolve this problem.
Regards,
Deepak.Hi
We had the similar issue and i think this is due to size of screen.
Try to arrange the fields in 2 or 3 columns, it may work
Regards
Madhan D -
Adding a new column to item overview screen 4900 in sales order transaction
Hi All,
I want to add a new column to refer to a custom field in screen 4900 ( Item overview screen ) in sales order transaction. Please suggest appropriate exit or BADI for the same. Give all steps to do the same.
Thanks in adavance.
Jawahar.Hi
As the link that RamKi let us know, this is a modification, so, I suggest to avoid. See SAP Note 862228 - Order reason for returns on item level for further information. I suggest to use the other enhancements in tabs.
Regards
Eduardo -
Hi everybody ,
im new in enhacement and expect support from this forum people , i have been given a requirement, while sales order creation and saving i have to read the ship-to-party field and change this field to default value .
My problems are that:
1> how i have to identify the exits for this.
2> the name FM to read the sales order for ship-to- party.
if possible then plz supply the sample code to read the sales order .
Thanx and regards
samirHi Samir,
<b>1</b>.
To create Sales order T.Code va01.
<b>2</b>.
To search EXITS in the T.code ,i have program .Just create program and paste this code and Execute it.
U will get EXITS if this T.code has.
*& Report Y_USER_EXIT *
report Y_USER_EXIT no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
if sy-subrc eq 0.
select single * from tadir where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = tstc-pgmna.
move : tadir-devclass to v_devclass.
if sy-subrc ne 0.
select single * from trdir where name = tstc-pgmna.
if trdir-subc eq 'F'.
select single * from tfdir where pname = tstc-pgmna.
select single * from enlfdir where funcname =
tfdir-funcname.
select single * from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
select * from tadir into table jtab
where pgmid = 'R3TR'
and object = 'SMOD'
and devclass = v_devclass.
select single * from tstct where sprsl eq sy-langu and
tcode eq p_tcode.
format color col_positive intensified off.
write:/(19) 'Transaction Code - ',
20(20) p_tcode,
45(50) tstct-ttext.
skip.
if not jtab[] is initial.
write:/(95) sy-uline.
format color col_heading intensified on.
write:/1 sy-vline,
2 'Exit Name',
21 sy-vline ,
22 'Description',
95 sy-vline.
write:/(95) sy-uline.
loop at jtab.
select single * from modsapt
where sprsl = sy-langu and
name = jtab-obj_name.
format color col_normal intensified off.
write:/1 sy-vline,
2 jtab-obj_name hotspot on,
21 sy-vline ,
22 modsapt-modtext,
95 sy-vline.
endloop.
write:/(95) sy-uline.
describe table jtab.
skip.
format color col_total intensified on.
write:/ 'No of Exits:' , sy-tfill.
else.
format color col_negative intensified on.
write:/(95) 'No User Exit exists'.
endif.
else.
format color col_negative intensified on.
write:/(95) 'Transaction Code Does Not Exist'.
endif.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
call transaction 'SMOD' and skip first screen.
*---End of Program
<b>3</b>.
Just click on the EXIT ,it takes u to SMOD transaction code .See the documentation for EXIT if it is maintained .
I hope this helps u little bit.
<b>Thanks,
Venkat.O</b> -
hi,
i need to eliminate leading zeros for PO number which comes in SO created trough ALE.i found the enhancement for the FM idoc_input_orders.in that enahancement we have 12 FM's.my Leading zeros are comming for field belnr which comes in e1edk01 segment of idoc orders05.now i had coded my part of coding in FM exit_saplved.._oo1 and i had activated that.but it is not working for me.than i tought of going to other FM exit_sapl..._009.in which i'm not able go into the include either.plz help me out.thank you.Hi, Krishna!
With IDOC_INPUT_ORDERS during IDoc interpretation PO number is assigned to XVBAK-BSTKD field which is later used for sales order creation with reference to PO.
So all you need is to use some customer exit with changing parameters containing XVBAK after IDoc interpretation is completed. For example you can use EXIT_SAPLVEDA_009 which is called at the end of IDoc check after interpretation.
Regards,
Maxim. -
User exit for sales order-Urgent
How Developed a User Exit, which will be triggered when a Sales Order is changed manually. This user exit will check the requested delivery date and update VBKD-BSARK field.
Pls help me how to do it....
Pts will be rewarded.....Hi,
The following exits trigger during VA01 creation:
EXIT_SAPMV45A_002 and
EXIT_SAPMV45A_003
Check this include MV45AFZZ also.
Regards,
Satish -
User exit for sales order creation VA01.
Hi friends,
While creating Sales order, before saving the document, I need to check the Customer (Sold to pary?) details in KNEX table. KNEX-KUNNR KNEX-TDOCO KNEX-DHRCO. if condition fails, I need to display an error message V1525,
which should contain
1)customer(sold-to -party?KNEX-KUNNR)
2)partner function PARVW (VBPA-PARVW?)
3)country LNDEX KNEX-LNDEX
Functional spec says, 1)V45A0002
2)V45A0003
3)V45S0001
4)V50EPROP User exits can be levaraged.
1)triggers before we enter customer (sold-to-party) in VA01. so may not be used.
remaining i tried, but I am not able to get the proper PARVW, LNDEX from function module parameters / structures like VBAP/VBPA etc.
Please help me the way.
i) the above user exits can be used?if not, help me with user exit name.
ii)if yes, how to fetch PARVW , LNDEX, KUNNR...as all the primary keys must be used in the selection query.
Please help me ASAP.Hi,
Use this enhancement V45A0002.
Reward points if it helps,
Satish
Maybe you are looking for
-
I have been trying to burn a CD-R at a slower speed but everytime I do so it comes up with Error 4260 and spits it out. I have tried a system reload and still can't get it fixed. I am trying to burn it at a slower speed b/c the CD will not play in
-
Can I copy a spreadsheet from Numbers into the body of an email message?
I created a basic calendar originally in Excel and have moved to Numbers. When I copy the Numbers spreadsheet calendar to the body of an email message, it loses all borders and formats and looks like a word salad. I need to paste it into the email me
-
My Playhead thing won't start at the beginning.
In every project when i hit play it starts in the middle of the song? :{
-
Hi everybody, I'm not a BSP developer. Mayby a very easy question, mayby also stupid, but I couldn't find any information about this topic so far. Can I consume Web Services in BSPs ?. Regards Peter
-
How do I convert an .ALF file?
Trying to convert .alf files my graphic designer sent over to me to .pdf because my computer doesn't recognize them. How do I do this?