Documente Academic
Documente Profesional
Documente Cultură
com/site/ipcdevelopment/Home
When a customer creates an order on the SAP CRM Ecommerce B2B or B2C applications. The following steps are undertaken for pricing to be triggered. Step 1. The customer inputs the values of the product he wishes to buy.
Step 2.
Depending on the Sales Area(Sales Org, Distribution Channel and Division) , Partner Determination Procedure and Document Pricing Procedure the Pricing Procedure on CRM system is triggered.(These are basically part of Base Customization of SAP CRM ) Step3. Within pricing procedure we have condition types , these are the various kinds of calculations required to find the total price of the item Step 4. Within condition types we have access sequence,the system reads the first condition type of the pricing procedure and determines the assigned access sequence. This step, together with the following , is repeated for each condition type on the pricing procedure. The system reads the access sequence with the condition tables. The sequence of the condition tables forms the search strategy for determining the individual condition records.The system reads the
IPC DOCU 2 https://sites.google.com/site/ipcdevelopment/Home first condition type of the pricing procedure and determines the assigned access sequence. If the system does not find a valid condition record for the first condition table, it carries on and searches for a condition record for the next condition table. .
Step 5.
system has found a valid condition record for a condition table, it makes the result available to pricing in the form of prices and discounts.
Once the
Step 1. Download j2se version 1.4 from http://java.sun.com/j2se/1.4.2/download.html Step 2. Use Netweaver Developer Studio or download Eclipse 3.1 from http://www.eclipse.org/downloads. Step 3. Create an empty folder like C:/IPC_DEV Step 4. Unzip the file attached to SAP Note https://service.sap.com/sap/support/notes/809820 in the subdirectory C:/IPC_DEV/PRC_UE_CUSTOMER
Step 5. Start the transaction /SAPCND/UE_DEV. Step 6.Download the libraries in the directory C:/IPC_DEV/PRC_UE_CUSTOMER.
Step 7. Start eclipse or NWDS and select as workspace the manual created folder (C:\IPC_DEV). Eclipse will create the meta data for an empty workspace Step 8. Select File Import and Import an Existing Project into Workspace. Select the PRC_UE_CUSTOMER folder as root directory. Eclipse should show the PRC_UE_CUSTOMER as project name Step 9. Now the JRE System Libraries have to be added to the build path of eclipse. Activate the context menu on the project (right mouse click) and select Build Path Add Libraries. Select JRE System Library and use a 1.4.x version Step 10. Prepare the API source and build the HTML documentation. Activate the context menu (right mouse click) on build_api_doc.xml and select Run As
􀃆Ant Build. Please ignore the error message thrown during that process
Step 11. Refresh the eclipse Project by right mouse clicking on the project and selecting Refresh (F5) in the context menu
IPC DOCU 2 https://sites.google.com/site/ipcdevelopment/Home In the transaction sm53,on the left side we can see Log Administration, in that we also see the Log Configuration. We can specify the various severity levels like at the package or class level. 1. Info 2.Warning 3.Erorr 4. Fatal 5.Debug Logs can now be viewed at the same transaction sm53. The log entries can also be filtered by different criteria such as Severity, Log Name (which is the class name or package) or User.
IPC DOCU 2 https://sites.google.com/site/ipcdevelopment/Home To make the debuging active we have to set the parameter PRC_RFC as X using the transaction su3 , in the tabs named parameter. This happens for the user for which we want the debugging to be active.
In the transaction sm 52 , you can see the status of the debugging , the various statuses are Not active: Debugger is not active Started: Debugging has been started Waiting: VM is waiting for the debugger client to connect Active: VM is connected to the debugger client Stopping VM is closing the connection to the debugger