BAPI with Sales Order User Information

Hi Guys,
I need BAPI Contains the User information of Sales Order like who created the sales order No of users Accessing the sales Order .Thanks in advance.
Thanks
Kiran.B

Hi
In the header data of any BAPi you will get the information who has created the sales order,
Who has accessed this sales order
you can see this info using SUIM tcode
Users who accessed this Tcode VA01/VA02
reward points if useful
regards
Anji

Similar Messages

How to create Delivery with sales order FM/BAPI

Hi Gurus,I'm new to SAP platform
I have created sales order ,
with this i need to create Delivery(vl01n)
so i need to give 'Shipping Point','Selection Date','SD Number'
so could any one tel me which FM/BAPI is suitable to create
Outbound delivery with 'sales order number', 'Selection date' and
"Plant or Shipping Point'.
With these Import parameters i need FM/BAPI .
Thanks in Advance
Siva Kumar kasa.

I have created delivery with that BAPI
giving 'batch number' but it was not updated,so can u tel me
any related field which need give to change batch field also.

Can u tell me any bapi to create the purchase req with sales order as refer

can u tell me any bapi to create the purchase req with sales order as reference?

Hi Mukesh,
You can use 'BAPI_REQUISITION_CREATE' for the purchase requisition creation if through transaction, you use transaction ME51N for creating the purchase requisition.
Cheers,
Sujay

PO Creation from Sales Order User Exit

Hi,
I have a business requirement where I need to create a Stock Transport Order (STO) for a particular kind of sales order. I outlined different options for achieving this functionality.
1. Trigger a workflow for creating STO.
2. Configure it an EDI output for sales orders. Using the EDI document, create STO in the same system.
3. Create STO using BAPI from the sales order exit 'USEREXIT_SAVE_DOCUMENT'.
I am trying to understand the issues if I go with option of creating STO from sales order user-exit. I tested it and it is working fine. But what concerns is me transaction integrity. In other words I am trying to execute another transaction within a transaction. Both Transactions (VA01 and ME21N/BAPI) may be trying to access same tables. Anyways I havent see any potential overlap.
I would like to know anybody implemented such a solution?
What could be the potential issues? Does it really affect transaction integrity?
Thanks A Lot
Anil

I would also be concerned with the possibility of the order failing to update AFTER you call the BAPI. You could create a custom output type that processes on order create for that order type. You could add your BAPI call to the processing routine of the output type.

Need All Sales Order user exit

Neeed all Sales Order user exits

Hi,
Check these Exits and their corresponding Programs
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.
Reward points if helpful.
Regards
Ravi

Opening and closing stock with sales order and with out sales order

hello,
any body please help me my client want to check opening stock and and closing stock in areport.
material contains batch and some material with sales order and some are with out sales order. my client is asking this in a single layout. please tell me isthere any teport or bapi or function module to get this report.
this is very uregent. and layout is requesting like opening stock, production stock, sales stock and closing stock.
please guide me to get this report.
Thanks & Regads
Bhakta

Transaction MB5B
For sales order related use specila stock as E and use radio button indicator in stock type
For stock w/o sales order, use special stock indiactor as "space' and stock type valuated stock.
to get a perticular month,opening stock/closing stock enter the start date/end date as month start and end date.
See the o/p which will give the stock as required by you

How to grow the report of customer's openitem with sales order

How to grow the report of customer's open item with sales order?
Now we can get the customer's open item with invoice No easily,but our end user need the the customer's open item also with sales order .And because a invoice to multi sales orders. I can do nothing.
Now I have a idea that a develivey No with one sales order , and one invoice with a sales order's develivery ,then one inovice to one sales order . I want to know if other company have use this idea. Or have other solution for my problem.

Hi Yuzhou Yang ,
Yes you are right. In FI transaction you can get the sales invoice wise , reference field of the header data.
As you are aware that while creating a sales order , no FI entry is generated.
In my opinion you can get the required report through customization.
Thanks
D.K.Lakshmi narayana

Issue with sales order stock that is referencing a non-existing sales order

We have an issue with sale order stock.
Due to user error we have ended up with a negative quant of sales order stock in a bin. Further the error was due to mis-keying of sales order number. Hence this negative quant is referencing a sales order that does not exist.
We need to get rid of this quant.
I thought of cycling this quant off as a solution. And hence replicated the scenario in the test system. I was able to create a TO to cycle it off but cannot clear the differences from 999 . The error I get while trying to do this is "SD document not in database or has been archived" . This error is true since the sales order actually does not exist. So cycling it off did not work.
Can anyone suggest how we can get rid of this negative quant of sales order stock ?
Thanks

Hi,
You said that your user mistyped the SO number and it resulted in a -quant. In which transaction was it possible? If I give a non existing no. SAP doesn't allow me to book.
If I were you I would check both in WM & IM what the user had done...step-by-step...
Negative quant comes to existance in interim storage type if we book e.g. a GI. It should have started in IM...how was your user be able to do that??? If it was possible cannot you reverse the IM booking?
(...if all else fails...cannot you create a SO document with external number assignment with the same number?...)
BR
Csaba
Edited by: Csaba Szommer on Jun 24, 2008 8:31 PM

Change Confirmed Qty in Sales Order User exit/ATP User exit

HI
We have a requirement to change the ATP Qty for certain meterials & Order Types duing sales Order User exit(FORM USEREXIT_MOVE_FIELD_TO_VBEP.? ) or ATP User exit.( ATP...OUT?).
Is this ok to update the XVBEP in FORM USEREXIT_MOVE_FIELD_TO_VBEP of MV45AFZZ ?
Our requirement will be like this, for one order type ZSAL( and for certain Materials) we need to reserve 4 qty, if any order comes with 10 qty and the confimed qty is only 6( total available stock at present) , then we should only confirm 2 qty for the other order type( For Non ZSAL Order Type), and reserve the 4 QTY for ZSAL Order Type.
If there are multiple schedule lines for an Item, we need to reduce the qty equally( as possible) from all schdule lines.
i.e. date1 qty 4
date2 qty 6,
in this case we should confirm Date1 QTY 2, date2 qty 4, so that the remaining 4 will be reserved for ZSAL Order type.
Whats the Best way to achieve this ?
Edited by: agrud agrud on Sep 8, 2011 4:01 AM

Hi Agrud,
Did you check the possibilities with configuration.If it is not possible with configuration then you can use that exit.Before i used this but only to display not to change any thing.
Regards,
Madhu.

Help needed with RA with Sales order scenario

Hello Gurus,
We are using SD-RR right now for our sales orders. We are facing difficulty with timing cost posting in that scenario and need your help with same.
When we do PGI cogs posting is done. RR usually happens at at later point of time after customer accepts the order. Out cost is booked before revenue recognition, which financially is bothering client. Client wants Cost and revenue recognized at same time.
I've heard that RA can be used with sales order item as cost collector. I want to understand how will it work functionally and what are the basic config elements.
If someone can explain step-by step I'd appreciate that very much.

Hi,
Follow the step
1) Create two user defiend Status for Sales order, one like X -Revenue & Cost to be recognised, and Y = ot to be recognised
2) Use Completed Contract Method in Expert more for Status Y and Revenue Based RA for Status X
3) Use Y as default Status in Sales Order. When you run RA, system will post costs to WIP and Revenue to Billing in Exess of Revenue. When ever you want to recognise revenue and Cost, change the status of the Sales Order as X, then Revenue based RA will be used.
Regards,
Rijo Paul

Sales Order User Exits - configurable materials !?

I have been tasked with investigating the following issue and if it can be solved via ABAP/User Exits. Users in an already live system are entering Sales Orders ( VA01 )with multiple Configurable Material line items and have to repeatedly enter the same characteristic values in each line item ( by entering Item Details >> Configuration ). They want to enter a set of characteristic values in the first line item and then have them defaulted into any further items. I have looked at the standard user exits in particular USEREXIT_MOVE_WORKAREA_TO_SDWA. Has anybody attempted anything similar to this !? Any ideas ?
Possible issues are:
1. How do I find the characterictic values from the 1st line item. ie. they haven't been saved yet, are they in a temp area similar to XVBAP for normal sales order line items !?
2. Are there are any suitable user exits in the Configuration side of things ( Function Group CEI0 !? ) to effect any changes the defaults. There are some BADIs in the code but they are not yet in use !?

Hi Jonathan!
I had a different requirement with sales orders and configuration, but this forced me into long debugging of behavior of all these exits.
1) Characteristics can't be read.
ad 1) in configuration it's possible to call function modules. Here (inside the configuration) values of characteristics are available and can be saved in global data of a Z-function module. This is later (in same transaction) available (like import/export).
2) I would propose to use functions of characteristics (as mentioned, it's possible to execute own function modules in configuration). It's possible to default values (meaning: output of your function is only done, if characteristic is not set) based on global data of Z-function module.
As long as a global memory is used, no interaction with other transactions has to be feared.
You don't need user exits (but a lot of coding).
You need to change the customizing of configuration - probably a huge task, because I guess you have a huge configuration (otherwise users wouldn't ask for maintenance help).
Regards,
Christian

Transfer Posting problem with "sales order stock type" status

Hello, i have this problem, i spend 2 days looking in the forum, but
nothing, the question is:
The SD users sell an item, and the item get the status of "sales order
stock type" in the MMBE, but at the same time, the MM user made a
trasfer posting in two steps, he take out material with transaction
MIGO, mvt 351, to another plant, but the materail was already
compromised with SD; now he cant sell the items, because he dont
realize that the material was in sales order stock type, and he already
transfer it to another plant. how can i block this? if a material in
MMBE is with "sales order stock type" status, he CANT transfer it with
351 mvt type, what config i have to make? thanks a lot!!!!
now the quantity of the unrestict use
stock is lower than the sales order, we dont want to have this issue,
thanks again
Edited by: Alex Arti on Aug 6, 2008 7:14 PM
Edited by: Alex Arti on Aug 6, 2008 7:16 PM

Hi!
Have you recently upgraded to EHP4? In this case, please, check the note 1441195. This note should solve the issue that you are reporting.
I hope this helps,
Esther.

STR pegging with Sales Order

Hello Experts,
I have a scenario in which STR (Stock transport requisition) is FIXED pegged with Forecast and Sales Order.The requirement is, I want to fulfill sales order only with this STR not the forecast.
I am able to change the STR quantity with the pegged quantity with sales order using BAPI ( ie: STR Qty = Pegged Qty of SO) But when I see the pegging overview, in product view (/SAPAPO/RRP3),System is fulfilling forecast first and then sales order.
I tried to change the STR quantity manually in product view,but still it is pegged with forecast first which I dont want.
I want STR to be pegged only with Sales order not with any other order.
Do this require any setting somewhere in SPRO? or this is a normal case in SAP APO? or Do I need to break pegging relationship first then create new pegging relationship with SO only?
Please advice.
Regards,
Saurabh

I think we can not break pegging and create new one with desired order.I am not using any SNP engine...
I have tried to change the STR qty but it is automatically respecting forecast first which i dont want to do....I changed order dates,Pegging Strategy in product master also but it is not happening......
I am talking about normal product view in which STR is fixed pegged with the SO and forecast,I want to change STR qty in such a manner that it should fulfill only pegged sales order not any other order.
Please advise me how to achieve this without any planning run?
Regards,
saurabh

Creating check on officers who can change a sales order - User Status

The user needs to create a check on persons who can change (User Status) on the sales order created.
The sales order are created by a group of people. These group of people can not be allowed to change the sales order - User Status(In header Detail).
Only a second level user users should be allowed change this user status.
Can it be done at configuration level. Or should we use an Exit?
Thanks in advance.

Hi Sunoj,
I never have used this auth. objects, but if you want to set restrictions on some users, search before in auth. objects. As I told you, you can use the tcode SU24 for this purpose. Do the selection, see the result, try it with tcode PFCG and check it.
If you can do something with customizing tools or other standard tools (as authoritation tools) avoid the use of enhancements, BADI, BTE'S and so on. If you don't find the solution, then go to userexits.
I hope this helps you
Regards
Eduardo

BDC for notification with sales order

Hi,
I have to code a BDC program for IW51 : Service Notification with sales order.
The problem is that in simulation mode (SHDB) the button "Sales order" is not working !!!
although it works well in transaction mode!
please help!
A+
Ihsen

hi all,
so anyone came across any BAPI or FM that creates Orders from Notification.
My requirement is similar to "Order Explode" functionality in WPS1 transaction (MEB). For two notificaitons, if the task list having the same operation and same type, then a single order gets created.
I want to know whether any FM/ BAPI is available that creates Order in reference to Notification. I just want to simulate Order creation.
Waiting for reply.
Debs

BAPI with Sales Order User Information

Similar Messages

Maybe you are looking for