IS Retail - Sales Transactions flow from POS to SAP
Hi All,
Can anyone tell about the process flow from POS (point of sale / third party software) to SAP in IS Retail ?
Bi,
Vamsi
Hi Vamsi,
unfortunatly I do not understand your request.
Do you want to setup this process or do you want to undersatnd the settings of the already running system ?
We need some more details:
Which POS system do you use ?
Is there a XI system or not ?
Do you use the POS DM (PIPE) system ?
The only things I know is that you have a POS (which one) and a ERP retail (which version).
Of course if you have a non-SAP POS it can be possible that you create some kind of IDOCs maybe via a mapper tool and call ERP inbound IDOC interfaces. This will also lead to a billing document.
POS IDOCs e.g. WPUBON, WPUUMS, WPUTAB,...
Look in customizing -> SD -> POS Interface -> Inbound
Regards
Björn
Similar Messages
-
Transaction Flow From AR to GL
Hi 2 all
Anybody know the transaction flow from AR to GL_ in functional and technical point of view .
Kindly post the reply with example .
Regards ,
ZulqarnainSandeep Gandhi, Independent Consultant wrote:
See http://www.oracleappshub.com/accounts-receivable/ar-to-gl-transfer-2/
Sandeep Gandhiit's for 11i
@OP
Re: Linking Table between AR to GL -
Booking Customer Advance from POS to SAP vide WPUBON
Dear All,
I have to post advance from customer received in POS to SAP customer account. This has to get posted vide Special GL indicator 'A' and linked to separate reconciliation account.
I am trying to send data vide idoc type WPUBON - but it does not have special GL indicator.
Please let me know if there is any other way to post customer advance from POS to SAP which should reflect in special GL.
Thanks in advance.Hi
KIndly check the idoc type FIDCCP01 to post the amount to special g/l indicator
prior to that configure the special G/L indicator in the t code OBXR
Regards
Damu -
Upload Sales order item from excel to SAP in VA01 thru frontend
Hi,
I am a front end user.
SAP version 710.
we enter sales order thru frontend in VA01 in SAP. The data is stored in excel.
Currently the following is performed.
Open VA01. In transaction entry screen ,
Copy from Excel & Paste In SAP the following
SAPID of the Customer
PO No.
PO Date
Then copy and paste the line items from excel block by block i.e. depending on no. of line items seen in SAP per screen, copy that many lines from excel and Paste in SAP.
Then select next block and
SAVE the order.
In excel there are many orders of different customers.
I know litte bit of VBA.
Can this be automated somehow.
Pl. help.
ThanksHi Suhas,
to automate the work in the SAP, it requires e.g. SAP GUI Scripting.
1. Please check whether your client is allowed to SAP GUI Scripting. (ALT / F12 -> Options -> Scripting -> Enable Scripting)
2. There should be only an indicator for Enable Scripting.
3.The other two indicators by Notify When ... should be inactive.
4.You would then be able to record a SAP GUI script. (ALT / F12 -> Script Recording and Playback... -> red dot)
5.Please record all that to what you have to do it manually for first record in Excel.
6.Stop recording (record and playback -> yellow dot)
7.Please then present the results here in the forum for your script.
8.Present us also your Excel sheet with some rows.
Unfortunately I have no access to the VA01 transaction. But you can already read a lot in advance on the following link.:
Re: Transferring data from Excel to SAP
Regards,
ScriptMan -
Sales Order uplaod from JAVA to SAP R/3
Hi all,
My cousin is working on uploading Sales Order Document
from java server to R/3.
for that he is having a code from JCO jar.
the below is the file from which one can upload his SO details from JAVA to R/3.
But in this program he is just able to upload one Item detail for one Sales document.
but requirement is to upload 'n' item details for one Sales document.
Here is the Java code.
@author pega
TODO To change the template for this generated type comment go to
Window - Preferences - Java - Code Style - Code Templates
Created on Jun 24, 2004
To change the template for this generated file go to
Window>Preferences>Java>Code Generation>Code and Comments
package com.sap.satyam.salesorder;
import java.sql.Timestamp;
import java.util.Calendar;
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.IRepository;
import com.sap.mw.jco.JCO;
public class SalesOrder {
static final String SID = "R3";
static final String errorID = "E";
IRepository repository;
//String orderNumber = orderCreation("M-01","3000","0002",3,"ST");
int counter;
public SalesOrder()
try {
// Add a connection pool to the specified system
JCO.addClientPool(SID, // Alias for this pool
10, // Max. number of connections
"800", // SAP client
"develop", // userid
"bslabap", // password
"EN", // language
"172.18.33.20", // host name
"00");
// Create a new repository
repository = JCO.createRepository("MYRepository", SID);
catch (JCO.Exception ex) {
System.out.println("Caught an exception: \n" + ex);
// Retrieves and sales order Create
public void createSalesOrder(String PO_NO, String MAT,String RQTY,String CUSTMAT, String SOLD_NAME, String SOLD_STREET,String SOLD_COUNTRY, String SOLD_POST_CODE,String SHIP_NAME, String SHIP_STREET,String SHIP_COUNTRY, String SHIP_POST_CODE)
try {
// Get a function template from the repository
IFunctionTemplate ftemplate = repository.getFunctionTemplate("BAPI_SALESORDER_CREATEFROMDAT1");
JCO.MetaData so_metadata = new JCO.MetaData("BAPI_SALESORDER_CREATEFROMDAT1");
// Create a function from the template
JCO.Function function = new JCO.Function(ftemplate);
// Get a client from the pool
JCO.Client client = JCO.getClient(SID);
// Fill in input parameters
// Header
JCO.ParameterList input = function.getImportParameterList();
JCO.ParameterList tables = function.getTableParameterList();
JCO.Structure input_header = input.getStructure("ORDER_HEADER_IN");
// Item details
JCO.Table table_item = tables.getTable("ORDER_ITEMS_IN");
//JCO.Structure input_item = table_item.getStructure("ORDER_ITEMS_IN");
// Partner details
JCO.Table table_partner = tables.getTable("ORDER_PARTNERS");
// Populate the header details
input_header.setValue("ZAD5","DOC_TYPE"); // Document Type
input_header.setValue("3000","SALES_ORG"); // Sales Organization
input_header.setValue("10","DISTR_CHAN"); // Distribution Channel
input_header.setValue("00","DIVISION"); // Distribution Channel
input_header.setValue("20041212","REQ_DATE_H");// can be changed in yyyymmdd (Requested date)
input_header.setValue(PO_NO,"PURCH_NO_C");// can be changed ( Customer PO Number )
//Populate the item detalis
table_item.appendRow();
table_item.setRow(1);
table_item.setValue("000010","ITM_NUMBER");
table_item.setValue("AA01","PO_ITM_NO");// can be changed
table_item.setValue("IAD-SC3000","MATERIAL");
table_item.setValue(CUSTMAT,"CUST_MAT");// can be changed
table_item.setValue("20041212","REQ_DATE");// can be changed in yyyymmdd
table_item.setValue(RQTY,"REQ_QTY");// can be changed Qty * 1000
table_item.appendRow();
table_item.setRow(2);
table_item.setValue("000020","ITM_NUMBER");
table_item.setValue("AA01","PO_ITM_NO");// can be changed
table_item.setValue("IAD-SC3000","MATERIAL");
table_item.setValue(CUSTMAT,"CUST_MAT");// can be changed
table_item.setValue("20041212","REQ_DATE");// can be changed in yyyymmdd
table_item.setValue(RQTY,"REQ_QTY");// can be changed Qty * 1000
//Populate the Partner details
// Sold to Party
table_partner.appendRow();
table_partner.setRow(1);
table_partner.setValue("AG","PARTN_ROLE");
//table_partner.setValue("0000002007","PARTN_NUMB");
table_partner.setValue("0000100067","PARTN_NUMB");
table_partner.setValue(SOLD_NAME,"NAME"); // can be changed
table_partner.setValue(SOLD_STREET,"STREET"); // can be changed
table_partner.setValue(SOLD_COUNTRY,"COUNTRY");
table_partner.setValue(SOLD_POST_CODE,"POSTL_CODE"); // can be changed
// Ship to party
table_partner.appendRow();
table_partner.setRow(2);
table_partner.setValue("WE","PARTN_ROLE");
table_partner.setValue("0000100067","PARTN_NUMB");
table_partner.setValue(SHIP_NAME,"NAME");// can be changed
table_partner.setValue(SHIP_STREET,"STREET"); // can be changed
table_partner.setValue(SHIP_COUNTRY,"COUNTRY");
table_partner.setValue(SHIP_POST_CODE,"POSTL_CODE");// can be changed
// Call the remote system
client.execute(function);
// Print return message
JCO.Structure ret = function.getExportParameterList().getStructure("RETURN");
System.out.println("BAPI_SALES_ORDER_GETLIST RETURN: " + ret.getString("MESSAGE"));
// Get table containing the orders
//JCO.Table sales_orders = function.getTableParameterList().getTable("SALES_ORDERS");
JCO.Field sales_order = function.getExportParameterList().getField("SALESDOCUMENT");
// Print results
String so = sales_order.getString();
String message = ret.getString("MESSAGE");
String message_type = ret.getString("TYPE");
if (message_type.equalsIgnoreCase("E")) {
System.out.println("Error in Sales Order Creation:" + message);
else{
System.out.println("Sales Order " + so + " Created Succesfully");
// Release the client into the pool
JCO.releaseClient(client);
catch (Exception ex) {
System.out.println("Caught an exception: \n" + ex);
// Retrieves and sales order Create
public void listSalesOrders()
try {
// Get a function template from the repository
IFunctionTemplate ftemplate = repository.getFunctionTemplate("BAPI_SALESORDER_GETLIST");
// Create a function from the template
JCO.Function function = new JCO.Function(ftemplate);
// Get a client from the pool
JCO.Client client = JCO.getClient(SID);
// Fill in input parameters
JCO.ParameterList input = function.getImportParameterList();
//input.setValue("0000002007", "CUSTOMER_NUMBER" );
input.setValue( "3000", "SALES_ORGANIZATION");
//input.setValue( "0", "TRANSACTION_GROUP" );
//input.setValue("PO_NUMBER_JAVA01","PURCHASE_ORDER_NUMBER");
// Call the remote system
client.execute(function);
// Print return message
JCO.Structure ret = function.getExportParameterList().getStructure("RETURN");
System.out.println("BAPI_SALES_ORDER_GETLIST RETURN: " + ret.getString("MESSAGE"));
// Get table containing the orders
JCO.Table sales_orders = function.getTableParameterList().getTable("SALES_ORDERS");
// Print results
if (sales_orders.getNumRows() > 0) {
// Loop over all rows
do {
counter++;
System.out.println("--" + counter + "--
// Loop over all columns in the current row
for (JCO.FieldIterator e = sales_orders.fields(); e.hasMoreElements(); ) {
JCO.Field field = e.nextField();
System.out.println(field.getName() + ":\t" + field.getString());
}//for
} while(sales_orders.nextRow());
else {
System.out.println("No results found");
}//if
// Release the client into the pool
JCO.releaseClient(client);
catch (Exception ex) {
System.out.println("Caught an exception: \n" + ex);
public static void main(String[] argv) {
SalesOrder so = new SalesOrder();
so.createSalesOrder("PO_NUMBER_JAVA02", "","0000000020000","121-223-2332-1231", "SOFTWARE SYSTEME GMBH-WE", "STREET-SH","US", "53125","SOFTWARE SYSTEME GMBH-WE", "STREET-SH","US", "53125");
//so.listSalesOrders();
>>>>Please if any of SDN users can help in resolving this issue. It will be very helpful to my cousin.Before:
//Populate the item detalis
table_item.appendRow();
table_item.setRow(1);
table_item.setValue("000010","ITM_NUMBER");
table_item.setValue("AA01","PO_ITM_NO");// can be changed
table_item.setValue("IAD-SC3000","MATERIAL");
table_item.setValue(CUSTMAT,"CUST_MAT");// can be changed
table_item.setValue("20041212","REQ_DATE");// can be changed in yyyymmdd
table_item.setValue(RQTY,"REQ_QTY");// can be changed Qty * 1000
table_item.appendRow();
table_item.setRow(2);
table_item.setValue("000020","ITM_NUMBER");
table_item.setValue("AA01","PO_ITM_NO");// can be changed
table_item.setValue("IAD-SC3000","MATERIAL");
table_item.setValue(CUSTMAT,"CUST_MAT");// can be changed
table_item.setValue("20041212","REQ_DATE");// can be changed in yyyymmdd
table_item.setValue(RQTY,"REQ_QTY");// can be changed Qty * 1000
Try to add:
//Populate the item detalis
table_item.appendRow();
table_item.setRow(2);
table_item.setValue("000020","ITM_NUMBER");
table_item.setValue("AA01","PO_ITM_NO");// can be changed
table_item.setValue("IAD-SC3000","MATERIAL");
table_item.setValue(CUSTMAT,"CUST_MAT");// can be changed
table_item.setValue("20041212","REQ_DATE");// can be changed in yyyymmdd
table_item.setValue(RQTY,"REQ_QTY");// can be changed Qty * 1000
table_item.appendRow();
table_item.setRow(2);
table_item.setValue("000020","ITM_NUMBER");
table_item.setValue("AA01","PO_ITM_NO");// can be changed
table_item.setValue("IAD-SC3000","MATERIAL");
table_item.setValue(CUSTMAT,"CUST_MAT");// can be changed
table_item.setValue("20041212","REQ_DATE");// can be changed in yyyymmdd
table_item.setValue(RQTY,"REQ_QTY");// can be changed Qty * 1000
Regards. -
Stop the sales order flow from r/3 to CRM
Hello Experts,
I have an issue regarding middleware:
In our process 1. we create a work order in r/3 from that we create a followup sales order in r/3 itself.
But the problem is once the sales order is created in r/3 that is flowing to CRM .
Our requirement is we have to restrict the flow between R/3 and CRM.
please send your valuable suggestions.
ThanksHi,
Try to de regester the queeuee in smqr transaction related to sales. May be it will work.
Regards
Srinu -
Dear all,
For the migration data project , to migrate sales transaction(contract) from our legacy system to SAP in a huge amount, we use LSMW with I doc processing, we upload the data with three steps :
1. first we upload the sold to party, 2.then we upload the ship to party,3.we upload the bill to party.
When im upload the sold to party, the system otomatically generate ship to party and bill to party with the same number BP as sold to party, so when i upload the ship to party, my contract become have two ship to party, and its also happen when i upload the bill to party. We have use the same method 6 month ago to our system and this situation doesn't happen back then(back then the system dosen't otomatically generate ship to party and bill to party with the same number BP as sold to party). Could anyone tell me what could be the problem? Thank you.
Regards
IndahDear Glenn,
I'm doing LSMW in CRM, just for information i already done building relationship for sold to party, bill to party and ship to party, one sold to party may have many ship or bill to party. And the data is really huge so i can't mantain which the main partner for sold to party each time, because they could have different ship to party,do you have another solution??
Thank you
Regards
Indah Puspita
Edited by: Indah Puspita on Jan 7, 2008 8:38 AM -
Depot Sales-Excise values are not flowing from J1iJ to VF01
Hi Gurus,
In Depot Sales: while doing excise invoive from T-code J1iJ Go to delivery -RG23D selection select the delivery number XXXXX Excise Group 51 and series Group: 50 ENTER - select the line item and click on F6 and here we have to click on excise invoice Button for capturing the Input excise duties for taking the reference. And the excise values are shown here correctly.
Issue: In VF01- when we are raising the commercial invoice , the duty values are not flowing from the J1IJ transaction. Instead the values are showing Zero for all the three condition types namely JEXP, JECS and JHCS. We have used the Pricing Procedure ZINDEP and 356 routine.
Inputs on this how to solve will be highly appreciated.. as we are in critical stage.
What are the checks to be ensured to Get the values flow from J1IJ to VF01.
Scenario: STO from Mfrg Plant to Depot and Depot sales to customer.
Me21N-Me29N-VL10B-VL02N-VF01-J1IIn-MIGO-(STO process completes)-VA01-VL01N-J1IJ-VF01(duty values should flow from the J1IJ referenced Excise Invoice) Correct me if I am wrong.
Any user exits, Notes please let me know. I could not find any. I have gone through the forum threads, which speaks about 356 routine, J1ID- checks etc.
Thanks&Regards
Sreekanth:Hi!
Am sure you would have captured the Excise at Depot with J1IG.
Also, have you saved the billing document to check the duties?
Thirdly, after save, again open the billing doc and go to Header-Conditions then Save. This part does not seems logical, but i am sharing my practical experience.
Please check condition records if any.
Regards
Arun -
Check for transaction interface failure from POS to POSDM
Dear experts,
Would like to see if in your experience, you have encountered any report or functions that allow users in POSDM to check if sales transaction from a particular store has failed to do the inbound interface from POS to POSDM?
I am personally not aware of this, so if there is no such report based on your knowledge, would you have any workaround solution that you can suggest me?
Thanks so much.
DominicLink for Duplication Check process: http://scn.sap.com/docs/DOC-47529
Link for info on POS DM: http://help.sap.com/saphelp_posdm/helpdata/en/4e/9617be3aec6ea9e10000000a42189b/content.htm
Hi Dominic,
There are certain validation checks we have in POS DM to validate the transaction data when it comes to POS DM. These validations are like Master Data check, Duplication check, Sequence check for missing transactions and so on.
You can find more about the same in the given link. I don't know my editor is behaving strangely so the link is on the top. I am not able to paste the links in editor links are coming on top. Might be my IE issue.
Regarding implementing such validation in POSDM for incoming transaction you can refer my posted document for Duplication check in POSDM. From this document you will get an idea about how to implement the validation check.
Let me know if you need any other information.
Regards,
Amit -
Revenue not flowing from Sales order to PS so no WIP in PS/WIP
Hi,
We are following PS with MTO scenario.
For calculating WIP in projects we are unable to get the actual revenue flow from Sales order to PS so entire amount in PS/WBS is sitting in WIP but its wrong.
User wants to do the Delivery and billing form Sales order only.
Can you please help us how to calculate the WIP in this scenaio.
Thanks,Hi,
Have you made the account assignment as WBS Element in the SO line item. Ift his is done, once you create an invoice from SO the actual revenue will get updated in WBS Element.
Regards
Sreekanth -
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 -
Sales Order Issue From CRM to R/3
Hi Gurus,
We have an issue where all Bulk ISS orders are showing up in the OTD BW reports as unreported even though they have been reported shipped. The issue appears to be, that for ISS orders only, the schedule line item number for the base bulk line, shows up as "4001" and not "1" as it typically does. The manual orders and all EDI orders do flow through with a schedule line number of "1", but not the ISS orders. Please investigate why this is occuring for ISS orders. .
Further to this issue ...
Order XXXXXX is a CRM order for sales BOM material and this order in R/3 has the schedule line item number for item XX as XXXX. It appears that all Sales BOM orders from CRM are getting the schedule line item number of 4001. Please debug and investigate as to where this is coming from.
It is basically abt Schedule line number instead of
1 it is 4001 ...
Please guide me
How I do I go abt this .. is there a bapi call that I need to refer to
Please help points guaranteed...Middleware are a set of transactions. For replication some tx are:
R3AC1 Objetos de Datos (Business and Condition Objetcs)
R3AC3 Objetos de Customizing
R3AC4 Activation of Delta Download
R3AC5 Adapter Object Overview (Customizing Download) - Initial Upload of Condition MD
R3AM1
R3AS Initial Load
SMQ1 qRFC Monitor (Outbound Queue)
SMQ2 qRFC Monitor (Inbound Queue)
You need to create a Site (r3) and suscription for replication in tx SMOEAC . The suscriptions area standard: product, business partner, sales document, etc.
Also you need defined filter for customizing replication and data replication in tx R3AS and R3AC1.
You can use best practice for replication. You can access on: http://help.sap.com/bp_crmv250/CRM_DE/index.htm. Access to "C03: CRM Master and Transaction Data Replication".
Some points...
Regards -
Billing is not flowing from CRM to R/3(in Lease asset accounting)
Dear all,
We are working on Lease Asset Management. In our operations CRM is the Front End and R/3 is the back end. The billing flows from CRM to R/3 through a background job.
The problem is, Some of the billing document got stuck in G error, that is "Error detected in transfer to accounting", While Transfering the billing documents through" /BEA/CRMB12 - Sales -> Billing -> Transfer Billing Documents to Accounting"
System throwing the two types of error messages
1. Object not known in CO ( Message Class IAOM / No. 028 )
2. For Comination: 4F20/INTP(*interim period*) ,Transaction Type is Not Mapped in R/3 Table: ZMAPBILL_COND
For the first type of error, The CO assignments in
1.IAOM_ASSIGNMENTS
2.IAOM_EXT_OBJ_INF
Entreis are maintained in these two tables. Please let us know any other settings to be maintained in FI/CO and LAM to resolve this issue.
Please respond ASAP
Thanks and Regards
PriyadarshiniHi Priyadarshini,
I do not have SAP CRM system in front of me, but the error # Message Class IAOM / No. 028 is shown when u r passing billing doc to R/3.
The error is more related to Internal Order Controlling area in R/3.
IAOM_ASSIGNMENTS has Contract guid / Billing guid for which IO posting is done. Message no 28 , i beleive no assignment found when posting.
check FM IAOM_GET_ACCOUNT_ASSIGNMENT which throws error.
Also as per my Leasing knowledge 4F20 will be passed to R/3, and there is setting for statical condition or non statical condition, check with ur FI lead
Hope u get some hint.
Regards,
Deven
Do reward points if u find useful answer -
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
NainaHi 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 -
please help me in finding the document flow from sales order to invoice.Give me some document in pdf.
SD Transaction Code Flow:
Inquiry / Document type IN
Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
Quotation / QT
Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP
Purchase Order PO
Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
Sales Order OR
Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP
Delivery LF
Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
Billing MN
Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.
To create vendor tcode is
xk01(create), xk02(change) , xk03(display)
Tables are lfa1.
To create custmer tcode is xd01, xd02, xd03.
Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.
Some of the basic steps for SD config in IMG:
1. Define atleast one Company Code
2. Define sales org, DC, Division, Soffice, Sales Grp
3. Define PLant, Shipping POint, Loading Point
4. Assign Sales org - company code
5. Assign Sales org- Dc & Sales org-Division
6. Assign Sales org + Dc - Plant
7. Assign Shipping point - plant & Loading point - Shipping point
8. Setup sales area & Assign Soffice - Sales area & Sogrp - Sales office
9.Define Sales doc type, Item Category & Scheduel Iine category + Delivery type, Billing type
10. Create partner determination, text determination & incompletion procedures
11. Create your own pricing procedure & text determination procedures (if you wanT0
12. Assign Sales doc type - sales areas
13. Determination of Item category, Scheldule line category
14.assignment of Storage location & Plant to Wearhouse no
15 .Create master data - Customer, Material, Cutomer material infor record, Condition & Output
16. Post stocks in plant
17. test by creating a sales order.
18. Set up all copy controls Sales doc - sales docs + Sales odc -delievry + Delievery - billing + Sales doc - billing etc
Define contracts, Item proposal etc as per requirement.
In short these are the some of the basic steps required to set up SD
Check these threads.
SD FLOW AND MM FLOW
SD Flow chart
The specified item was not found.
Maybe you are looking for
-
Firewire target disk mode question
I am using firewire target disk mode to copy some files, but can only see the system drive on the slave computer, what do I do so I can see the secondary hard drive on the slave computer?
-
I reset my login on my ipad two days ago, today I can't remember what I changed it too. My Ipad is disabled and I was told to connect to ITunes
-
Delivery to be picked from JIT
Hi, Ineed the delivery to be picked from JIT and not from forecast.How to go about this. Murugan
-
Is thier a reason haveing a for loop in paint would cause a problem
when i have a gui
-
PSA SE and PS Elements 5.0 Sharing the Same Catalog
Is it possible to set up PSA SE and PS Elements 5.0 to share the same catalog? I really like PSA SE for a nice viewer that add the cataloging aspects. The PS Elements Organizer is nice, but takes too long to load, is too big in memory, etc. I have fo