Uaable to create a sales transaction

Hi,
I'm trying to create a Sales Transaction for a business partner. But I'm getting a error "No valid sales channel for this business partner. Enter a Sales Channel in the business partner's sales area data."
I already have entered the Sales Area data.
Please advice.
Thanks in advance.
Sandeep

Hi All,
Thanks for your response.
Well, I had done one basic mistake. The Sales Org did not have the Mobile Sales employee mapped to it. I did that and replicated the org structure to the Mobile Client.
But now when I try to create the Sales transaction, I get the following error.
"The combination of sales area and sales transaction type is not valid."
Please advice.

Similar Messages

Error message while creating Sales transaction

Hi Gurus
While creating a sales transaction in Mobile Sales I am getting the following error message.
No Valid sales channel exists for this business partner enters a sales channel in the business partner sales area data.
I have checked in table SMO_KNVV, there is an entry for this business partner. What can be the possible reason? Please help.
Regards
Javed

Hi Javed,
Your logged employee should also have some sales area assigned to him/her.
This can be done by assigning you employee to sales position under sales area in CRM Org Management (PPOMA_CRM).
Once this is done and org. data is replicated to Mobile. you can very much create the transactions without error.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

Not able to create Follow up transaction since it has been grayed out

Hi Experts,
We have a scenario where in we will create the Sales Transactions (OR) in ECC and then it will replicates to CRM.
In CRM we wants to create Returns Order (RE) as a follow up Transaction to OR (which is replicated from ECC to CRM) .
When I tried to create Returns Order (RE) in CRM as a follow up document to Sales Transaction (OR), the follow up Transaction CRM Returns (RE) has been grayed out. I mean it is in display mode only.
And then I created Sales Transaction (OR) in CRM itself and then I tried to create follow up Returns Transaction (RE) I was able to create.
But I am not able to Create Returns Order (RE) for the Sales Transactions (OR) that have been replicated from ECC to CRM.
Can anybody help me in resolving this issue. Any help ful answer will be rewarded with points.
Thanks in advance,
-Frederick Johnson.

Hi Fredrick,
Please check, whether you have completed all the steps for Copying Control for Business Transactions in the following path in IMG:
SPRO->Customer Relationship Management->Transactions->Basic Settings->Copying Control for Business Transactions:
- Define Copying Control for Transaction Types
In this step, you define the control for copying business transaction types.
To do this, you enter a source tranaction type and a target transaction type, and define the corresponding conditions for this combination.
- Define Copying Control for Item Categories
In this step, you define the control for copying item categories.
To do so, you enter a source item category and a target item category, and define the corresponding conditions.
- Define Item Category Determination when Copying
In this step, you define a specific item category determination which should be run during copying. The item category is used to find the target item category in the source transaction for the transaction type in the target transaction. This means that the transaction type for the source transaction is not relevant for the item category determination.
If the system cannot find an entry for the copying transaction in this table, the item category is found in the target transaction using the normal item category determination.
This might help you
regards
Srikantan

Regarding XIF Interface and Sale Transaction in CRM

Hi,
I have done the configuration in CRM system using XIF interface to communicate with other system.
We are in the process of implementing CRM, Product and Partner data has to upload in CRM. We are not using R3 for anything.
When i create a sales transaction using transaction code CRMD_ORDER,System allow me to save/create a business transaction even though i can see the error attached to it and at the same time I can see the BDOC number in SMW01.
But i dont see any relevant OUTBOUND IDOC against the BDOC, evenif i have configured it for external system and I was expecting Outbound IDOC with error status, please correct me if i am wrong.
I am using WE02 and WE05 to see my outbound idoc and i have not found anything here.
Am i missing some step in configuration which is required for converting BDOC to IDOC, Please suggest me.
Steps which i followed to configure the system are
1. Create a suitable RFC destination in the SAP IMG Define Target Systems for RFC Calls .
2. Create a logical system.
3. Create a receiver port (transactional RFC) in SAP IMG Define Port, indicating the RFC destination you created earlier.
4. Create a partner profile, for example, partner type LS with the partner number CRM_XML_BC, in the SAP IMG Maintain Partner Profile Manually.
5. Enter all outbound parameters for the logical system CRM_XML_BC in Create Outbound Parameters in the Outbound Parameters window .
6. Create a site (transaction SMOEAC). To do this, select Object Type Sites and Create Object. Assign your site a suitable name and select Site Type External Interface for IDocs. Assign the partner profile created previously as a Site Attribute.
7. Use object type Subscriptions to maintain a subscription for publication of the object with the predefined site.
8. Create an entry for the new site using XIF customizing transaction CRMXIF_C1 via F4 help (BDoc Type = <objname>, IF Type = 'CRMXIF_*_SAVE_M', Set relevant flag for complete Data and Return). The flag Flag for complete data is only relevant for the objects "order", "business partner", and "business partner relationship". It flags whether only delta changes or the object instance should be transferred completely. The object "business document" is always sent completely, regardless of flag status.
Thanks & Regards,
Manoj Tiwari

Hi Joao,
Thanks alot for your quick reply.
Yes i have selected "post it immediately" instead of "collect Idoc". should i select "post it immediately"??
About the Outbound parameter i specified everything like message type (crmxif_order_save_m), port , RFC destination of type R3 since we have SRM system, basic type (crmxif_order_save_m01), package and post the idoc immediately.
Here in our distributed environment we are sending data from CRM to SRM, means our target system is SRM.
I have created the Site of site type "External interface for idocs" and give the partner Number of SRM system and created subscription too as part of XIF setup.
Please reply me if i am going wrong in my approach.
Thanks & Regards,
Manoj Tiwari

Process types and Sales Transactions not Sync with SM2.5

Hi Experts,
1) We have custom process types for leads, opt and quotations etc.. but the TYPES option is not activated or greyed out when creating any sales transactions from app SM 2.5.
Please help on this.
2) With our accounts as a relationships, leads and opportunity are syncing well but not quotations and activities. Is there any settings for that which needs to be activated.
Thanks for your help.
Thanks
VS

Check out these instructions: http://support.apple.com/kb/ts5223

Error in Sales Transaction in CRM 4.0 ?

Hi All,
We are working on CRM 4.0 i have created a sales transaction in WEB and transaction will see in CRM and it is getting downloaded to R/3.
But when I go back to CRM and check Sales Transaction it is showing me error as "An error has occured in the system XYZCLNT100 while copying the document".
And i have been check in SMQ1&SMW01 ..in both T codes there is no error ..
How can i figure out this problem ?
can anyone help me in this regard?
Thanks in advance.

Please look into note 490932 for any issues of this nature
This note gives an insight into possible error causes during the download or upload of sales transactions between CRM and R/3 and helps you correct these errors. This note is relevant for CRM Release3.0.
It is also relevant for releases higher than 3.0.
Other terms
Download, initial, delta, delta download, SALESDOCUMENT, BUS_TRANS_MSG, event 00501014 501014
Reason and Prerequisites
The error causes may be included an incorrect configuration or missing system settings. The note only focuses on the sales transaction-specific configuration of the data exchange, but not on the settings for CRM Middleware in general or for other CRM Server applications.
Solution
In CRM Release 3.0, the following sales document items are transferred to the R/3 System:
Sales items
Customer return items
Substitute delivery item
Credit memo request items
Debit memo request items
As a leading system for the order entry, CRM only transfers data to the R/3 System if it is relevant for the logistical subsequent processing (delivery, billing). For this reason, requests for quotations and quotations themselves are not transferred to the R/3 back-end system with the standard delivery. With SAP note 455678, you can use a modification solution to also transfer quotations entered in CRM to the R/3 back-end system.
           Restrictions of note 455678:
If you are using this solution, you cannot create any sales orders with reference to customer quotations in CRM.
Mixed document processing (partially customer quotation items and partially sales order items) is not supported in the R/3 System and is therefore not possible during the quotation upload. The solution specified here only performs the upload for documents that consist of quotation items only.
The quotation items must be defined in the Customizing for copying. This solution does not cover scenarios where the order is generated from the quotation as a result of a status change. Therefore, quotations entered in SAP Internet Sales (in particular) cannot be transferred to the R/3 System.
Only completion rule 'A' ('Completed with one-time reference') is supported in the R/3 System.
Sales transaction-specific settings for the data exchange
1. Basic administrative settings for the replication of sales transactions
a) The BDoc relevant for the distribution of all transaction types is called BUS_TRANSACTION_MESSAGE. In transaction SMOEAC, the relevant R/3 site must be subscribed to the corresponding publication 'All Business Transactions (MESG)' so that sales documents can be distributed to the R/3 back-end system. (To create a subscription, select the 'Subscription' object type in the 'Object type' selection list in transaction SMOEAC and then select the 'Object -> Create' function from the application menu or the corresponding symbol from the application function bar. The Subscription Wizard, which supports you during the creation of a new subscription, is started as a result.)
b) Check to see whether the current CRM release has been maintained in the R/3 back-end system in the CRMPAROLTP table. This has to be taken into account in particular after an upgrade. You can maintain the CRMPAROLTP table in transaction SM30 in the R/3 back-end system:
                       Parameter name "CRM_RELEASE"
                       Param. value "30A"
c) Event 00501014 must be activated in the R/3 back-end system so that the delta download of sales transactions from the R/3 back-end system to CRM works. The event must also be active for the upload of sales transactions from CRM to R/3.
d) The event is activated automatically after a successful initial download. Call transaction R3AC4 ('Object Class Activation') in CRM and check whether the following entries exist:
                       Object class "BUSPROCESSND"
                       RFC destination <R/3 destination>
                       Select your entry and then choose 'Events by Object Class' (branch to the TBE31 table in the R/3 back-end system). The following entries must exist:
                       Event "00501014"
                       Obj. class "BUSPROCESSND"
                       Function "CRS_SALES_COLLECT_DATA"
                       If you do not see these entries, your initial download was not completed successfully.
e) In transaction BD97 of your CRM system, the R/3 back-end system must have been maintained as the standard BAPI destination. Check the V_TBDLS view to see whether your R/3 back-end system has been defined as a logical system. A termination message in the SAPLCRM_ DISTRIBUTED_LOCKING program when you call a transaction in CRM indicates the missing destination assignment.
Refer to notes 597812 and 674487. According to note 597812, the cross-system lock is processed using the RFC destination of the CRM middleware (SMOF_ERPSH table). However, the aforementioned entry in transaction BD97 for the Standard BAPI destination is still used to branch via the document flow to the R/3 system.
f) In Release 3.1I, you can only have one entry for the RFCDEST field (RFC destination) in the CRMRFCPAR R/3 table.
2. Definition of sales transaction-related Middleware parameters
a) If you do not want a BOM explosion to occur for document items in CRM during the transfer to the R/3 back-end system, make the following settings in transaction R3AC6:
                       Key "R3A_SALES"
                       name "NOSTRUCTURE"
                       value "X"
                       This would make sense, for example, if you have already carried out a BOM explosion on the mobile client and if you do not want a new BOM explosion in the R/3 back-end system.
                       Make sure that the assigned item numbers in the sales transaction/sales document are set differently for main items and subitems so that no item numbers are assigned twice after the transfer and the BOM explosion in the R/3 System. The item numbers of the main items must be set identically in CRM and R/3. For more information, see note 496906.
                       Example:
                       CRM sales transaction
                       Pos.Nr.   Item No. Product
                       100 MAT1
                       200 MAT2
                       R/3 order
                       Pos.Nr.   Item No. Material
                       100 MAT1
                       101 Subitem1
                       102 Subitem2
                       103 Subitem3
                       104       ...
                       200 MAT2
                       You can maintain the item number assignment for the transaction types (CRM) or for the sales document types (R/3) in the Customizing.
b) If a document is created in CRM and transferred to the R/3 back-end system, the warning messages of the transferred R/3 back-end document can also be displayed in the CRM document. In this way, you can recognize, for example, in the CRM document whether the transferred R/3 back-end document is incomplete and has to be postprocessed so that it can be further processed logistically. For this purpose, make the following settings in transaction R3AC6:
                       Key "R3A_SALES"
                       name "COLLECT_WARNINGS"
                       value "X"
c) When you transfer a CRM document to R/3, you have the following control options with regard to pricing:
                       Key "R3A_SALES"
                       name "PRICINGTYPE"
                       value
                                         'B' = new pricing
                                         or
                                         'C' = copy manual pricecomponents,
                                         redetermine others
                                         or
                                         'G' = Copy price components unchanged,
                                         redetermine taxes (this value is
                                         delivered as a default setting)
3. Definition of the R/3 dummy division in CRM
              Note that no division exists in CRM in transactions at header level. In the R/3 order, however, the header division is a mandatory field. Thus, the R/3 dummy division must be maintained in CRM Customizing so that it can be determined during the transfer of a document. Otherwise, the order cannot be transferred to the R/3 back-end system.
              Customizing path: 'Customer Relationship Management -> Master Data -> Organizational Management -> Division Settings -> Define Use of Division and Dummy Division'.
              The use of several dummy divisions can be programmed in the CRM_DATAEXCH_AFTER_BAPI_FILL BAdI in the CRM_R3_SALESDOCUMENT_UPLOAD function module.
Hints for the initial download
Filter settings
In transaction R3AC1, you set the filters for the initial/delta download of business objects. In the SALESDOCUMENT business object, you can set the filters for the order download from R/3 to CRM. For successful execution of the initial download, you have to set at least the VBAK-ERDAT filter criterion (document entry date) for the SALESDOCUMENT business object. This filter setting is required for the successful completion of order downloads.
After you have completed these filter settings, you have to transfer these settings to the R/3 System. Select 'Filter sync.(R/3)'.
Choose your R/3 System as a source site and check whether you are using the VBAK-ERDAT filter criterion:
Example:
Table/Structure Field OP Low
VBAK ERDAT Greater than <Date>, for example, 20020128
The date must be entered in the same form as it is stored on the database (YYYYMMDD)!
The following filter criteria are also available:
VBAK-AUART Sales document type
VBAK-SPART Division
VBAK-VBTYP Sales document category
VBAK-VKORG Sales organization
VBAK-VTWEG Distribution channel
We recommend that you also use sales document numbers (VBAK-VBELN) as a further filter criterion. With this criterion, you can carry out an initial download according to sales document number intervals. The advantage of this filter criterion is that if your initial download terminates due to an error, you can restart the download after correcting the error as of the sales document number for which the error occurred. In this way you avoid having to restart a download for sales documents that have already been replicated.
Example:
Table/Structure   Field          OP            Low           High
VBAK             VBELN          zwisch.        0005000000    0005099999
Enter the field contents in the same way as it is stored on the R/3 database (leading zeros).
If you want to use this filter criterion, go to transaction SM30 and make the following entry in the SMOFFILFLD table:
Object name Table/Structure name Field name
SALESDOCUMENT VBAK VBELN
Note 497327 deals with possible filter-specific problems during the delta download that can occur due to missing R/3 back-end entries.
Block size
In this context, the block size specifies how many documents are selected in a transaction and transferred to CRM as a BDoc. The block size is defined on the system. The default value may have to be set to a lower value if problems occur (for example, memory overflow during the selection in the R/3 System). If the initial download terminates, check the dump log in the R/3 System (transaction ST22). The TIME_OUT or STORAGE_FREE_FAILED runtime errors indicate that the block size is too large. In this case, reduce the block size and restart the download. In addition, you can clarify with your Basis Administration whether the rdisp/max_wprun_time kernel parameter is large enough (this avoids a TIME_OUT error).
Basically, you should only download a few documents during the first download to check whether the system settings are correct. In this way, you can identify possible Customizing errors and correct them before the large load.
Queue processing during the initial download
In the case of very large transfer data sets, it may make sense to process the initial download in parallel within one object (object-internal parallel initial download) to complete the initial data transfer faster. Note 350176 describes the corresponding procedure.
Queue processing during the upload/delta download
Queues in CRM are defined in the SMOFQFIND table (for example, from CRM to CDB or from CRM to R/3).
For the BUS_TRANS_MSG BDoc type, the default setting of the queue processing is that all orders for a customer are processed in one queue.
As an alternative, you can set the queue processing in such a way that each order is processed in a separate queue. As a result, an individual order can no longer block the processing of other orders if an upload problem has occurred.
If you prefer this queue processing, go to transaction SM30 and make the following change in the SMOFQFIND table:
Select the BUS_TRANS_MSG BDoc type and change the segment field name from QUEUE_NAME to OBJECT_ID.
In the same way, you can also set the queues for the delta download in the R/3 back-end system in such a way that each order is processed in a separate queue. If you prefer this queue processing, go to transaction SE16 in the R/3 back-end system and make the following change in the CRMQNAMES table:
Select the entry for the SALESDOCUMENT object and change the BAPIFLD field from SOLD_TO to DOC_NUMBER (with BAPIOFFSET=3 and BAPIFLDLEN=10). Leave the second entry for the SALESDOCUMENT object (with QOBJPART=SAL_ERR) unchanged.
In transaction SMQR, check to see whether the queues have been registered or check transaction SMQS to see whether the destinations have been registered because otherwise, the queues are not processed automatically, and this can lead to queue overloads.
Check the queues regularly.
Composite SAP Note 504090 covers all notes that solve known problems in the transfer as of Support Package 06 (SP06).
Document cannot be maintained in online mode
If you cannot maintain a document, this can have various reasons. Basically, a sales document entered in CRM is locked until the R/3 System has confirmed the update of the order successfully.
If message CRM_ORDER019 "Document will be distributed - changes are not possible" occurs in CRM, check the queues (transaction SMQ1 and SMQ2). To analyze the data exchange from CRM to R/3, refer to note 431345.
If message CRM_ORDER013 "Transaction &1 is being processed by user &2" occurs in CRM or if message V1042 "Sales document &1 is currently being processed (by user &2)" occurs in R/3, the document is processed in the other system respectively. To avoid inconsistencies, a cross-system lock is set during the processing of a replicated transaction so that the document cannot be processed simultaneously in two systems.
Other notes
Only error-free sales documents are distributed to the R/3 System. If, in R/3, you change a sales document that was originally created in CRM, these changes are not transferred to CRM. That is, you should always make the changes in the original CRM document to ensure the consistency of the document data in both systems. Sales documents entered in the R/3 System are transferred to CRM, but they are locked for processing there. Changes to a document created in R/3 are also transferred to CRM.
In your settings for the data exchange, also make sure that the document number ranges correspond in both systems. For the successful sales document exchange between the systems, the transaction types and item categories have to be created in exactly the same way in both systems. If these objects do not exist in one system, you have to create them manually.
In transaction CRMM_BUPA_MAP, you can determine into which R/3 customer number the CRM business partner is converted and vice versa. If you do not receive a conversion for the specified business partner here, this indicates that a transfer problem has not occurred in the sales document but during the business partner download.
Header Data
Release Status: Released for Customer
Released on: 02.05.2006 15:04:13
Priority: Recommendations/additional info
Category: Consulting
Primary Component: CRM-BTX-BF-IF R/3 Interface for Business Transactions

How to restrict a Sales Transaction being created Straight up

Gurus,
We have a business requirement where a perticular Order type (Sales Transaction) can only be created as a follow on Order.
But the problem is, when i configure the Sales Transaction type, it is also appearing in the standard Transaction type list.
I have configured this Order type in the follow on Transaction configuration, but i cannot remove/hide this transaction type from standard transaction type list.
Pls advise.

Gurus,
I would really appriciate some help here.
Thanks in Advance.

Creating action in CRM sales transaction to trigger RFC in R/3?

Hello gurus
We wish to replicate our contracts from CRM to R/3 but since SAP is not supporting it, I heard that one option that we have is to enable actions in our CRM sales transactions, which when executed will trigger an RFC call to R/3 system and then create same transactioon there as well...
Could anyone please shed some light as to how this can be done?
Please advise.
Regards
Jai

Hello,
I should prefer using the ORDER_SAVE Badi, using a queued RFC to create the dat in the R/3 system.
Regards,
Fred

Unable to create sales transaction in POSDM though BAPI

Hi
ICurrently I am trying to create sales transaction in POSDM which is coming from POS thru XI to POSDM. But the BAPI /POSDW/CREATE_TRANSACTIONS_EXT is throwing an error
" Error determining sales item category for code 2001"
It was working perfectly fine in development. I have imported all transports from development to quality sytem. we also have BI plant and article data in our system. But not sure if anything other than this needs to be done.
Thanks
Naina

Hi Amit,
I would recommend you to raise the same query in the forumSAP CRM: Mobile Applications which is dedicated to queries related to mobile application and where you have more chances of getting the answer.
<b>Reward points if my post helps!!</b>
Best regards,
Vikash

Table to find sales order created for a transaction type.

Hello all
I have a requirement that i need to check all the orders created for a transaction type and to find out how many of them are active now and how many of them are deleted.
i know only the transaction type and based on this input i need to know the above details is there any report or table for this.
Thanks and Regards
shanto aloor

Hello shanto aloor,
in the database table CRMD_ORDERADM_H you can search by transaction type. In Se16 you can enter the process_type to find the related transactions. If you have the header GUID you can use also the report (SE38) CRM_ORDER_READ to get more details of the transaction.
Hopefully this information will help you to meet your requirement.
regards
Rene

Create multiple sales orders from single service notification?

Is it possible to create multiple sales orders from a single notification (IW51)?
We currently create sales orders directly within transaction IW51 (Create Service Notification). We kick off the sales order creation by pressing the "SALES ORD." button in the notification screen. We're now interested in creating a 2nd Sales Order which would tie directly to the same Service Notification. This is so that we can have the second order assigned to a different account assignment WBS (there are two different parties doing work on the service notification).
I assume you would have to go to VA01 to create the Sales Order, but am not sure how to tie it directly to the service notification from here. I treied to do a create with reference, but there is no ability to create with reference to a service notification.
Do I have to create a second service notification for the 2nd Sales Order for this to work? I want to avoid doing this if at all possible.
I'm running SAP R/3 Enterprise
Thanks for your help!

Hi,
go to vtaa- copy controls for sales document to sales document.
select your combination of order and quotation go to item level. There select value 0(zero) in field positive/negative negative.
No need to change update document flow.
After setting zero in copy control that be told on above. create order with respective to the quotation.
After saving the order.
go to document flow to see the status in between quotation and order.
If you placed setting right, then u certainly observe for quotation status will be open. so you can create no. of sales order with respect to that quotation..
Have a good day..

Problem in creating a sales document

Hi,,
I am creating a sales document programatically by the FM BAPI_SALESDOCU_CREATEFROMDATA1 for tht i have desigend ny selection screen in tht my requirement is i will not give item category for tht i have to quiery for given material and for given plant i have to fetch itcat plz help me in writing this quiery
vbap table is not coreect as it will store data after complettion of sales document
but here i want quiery to create a sales document it self
i have seen in transaction VA01 ity is getting data from t184 for itcat plz help me in writing this quiery
for good answer i will reward points

You can use the t.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Your issue is sorted!!
And further to your query for minimum price PMIN refer to my answer, you will not have to maintain any condition record or the price entered here does not reflect in any other document.
Regards,
PATHIK

Limit transaction types when creating follow-up transactions

Hi! We are operating in CRM 5. We have a requirement to only display certain tasks when creating followup document from an existing activity. Now, I thought that the copy control configuration would do the trick but I still see a big list of tasks, activities and sales transaction types appearing on the screen (as good as creating a new independent document). Can someone please confirm whether this requirement is at all possible in CRM 5?
Cheers!
SF

Hi,
We had a similar requirement. We used implemented CRM_ORDER badi and used the method ENQUEUE.
We wrote a logic to check the object type and process type of the transaction and also its doc flow.
If there is no doc flow available a logic is written to throw an error message as no standalone document can be created.
You can try implementing this badi and write a code in it.
Also you can throw custom message if user tries to created standalone orders.
Regards,
PP

Material Listing Error while creating the sales order

Hi Guru's
I have mantained a material in the lisitng for A002 combiantion for SO/DC/Pric. ref. material
While creating the sales order is throwing an error as material is not listed so the transaction is not possible.
I have done the basic invetingation on the folowing aspects
1)checking the material in the listing
2)Validity periods
3)Material not blcoked
4)Mateial is extened for the respective sales org
Kindly help ASAP.
Thanks & Regards
Tarakaram

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

Payment Terms in Sales Transaction...!

Hello,
I am basically an SD consultant. I am not familiar with CRM much.
I have an issue with the Payment Terms in a Sales transaction. It shows different Payment Terms at header and different at item. There is nothing in a Docuemnt's change log. May be user has changed the Peyment Terms is changed while creating Sales Transaction, but the user says he/she had not done so.
This caused a mismatch of Payment Terms at header and item level in R/3 Sales Order and so in Final R/3 Invoice.
What can be the issue..?
As in R/3 the Payment Terms is retrived from the customer master, in CRM also it should be the same as I believe. But I first would like to check the Customer Master (Business Partner) in CRM in Transaction BP. But within Transaction BP where to check the Payment Terms? The Sales Area Data button is there but not active.
Thanks in advance.
Best Regards,
HP

Hi Hardik,
To check the business partner payment temrs, you much change the 'role' of that business partner to, for example, 'sold-to-party' or 'payer'. Then the sales area button will became available so you can check the sales area dependent information, like payment terms.
Can you check?
Kind regards,
Garcia

Uaable to create a sales transaction

Similar Messages

Maybe you are looking for