Business Flows for Sales and Contracts process

Hi,
I needs Business Flows for sales and contracts process for my project.
Does anybody knows where i can find these BFA ?
Thanks
Regards
Mehdi

Hi mehdi;
Please check below and see its helpful:
R12 Responsibilities And Roles Based On Business Flows [ID 406401.1]
Regard
Helios

Similar Messages

Detail business flow for sd and mm

any body have the business flow for the sd and mm . please give me the link............if other modules also these ple pass the link ......

link: [http://www.sap-basis-abap.com/sd/sap-sd-processing-flow.htm]
link: [http://www.sap-basis-abap.com/mm/sap-mm-tables-link.htm]
link: [www.sap-img.com]
regards.
santhosh reddy
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Jan 30, 2008 2:39 PM

Basic process flow for WM and putaway process

Hi all,
Can someone explain me the basic process flow in decentralised WM system???
Also what do the foll terms mean in aWM process:
1.Putaway process
2.Putaway label
3.Selling Unit label
4.MIC #

In decentralized Warehouse, normally Inventory is managed in in a seprate application. SAP System will coordinate with it through IDOCS. For example, Sales Order and Outbound Delivery created in SAP Systems. Delivery is communicated to Decentralized Warehouse using an IDOC. Then Picking happend in the external system.
1.Putaway process: The process of placing the stocks in the appropriate Bins in a Warehouse. It starts after GR is done for a Inbound Order
2.Putaway label: Its a label that will beprinted with some basic information like destination bins
3.Selling Unit label: Again label
4.MIC # : Management of Internal Controls

Is there a Business Object for Sales Order Create and Change VA01 and VA02

Hi experts -
I am looking for a business object for Sales order create and change VA01 and VA02 respectively?
Thanks,
Mark

Hi Mark,
I think this question is best answered in [SAP Solutions|/community [original link is broken]; Forums.
- Subhodeep
Edited by: Subhodeep on Aug 29, 2009 11:14 AM

Consignment sale and contract difference

What is the basic difference between consignment sale and contract ?
Thank u gurus

Consignment Sales is a sale, in which initial ownership of the stock is with us, the stock being in the premises of the customer. The ownership is transfered on sale of material.
Contract may be quantity contract or Value contract, in which the stock remain in our owm premises, but it ia an agreement to delivery some'x' quantity of material or materials to the tune of decided valuue.
Consignment Stock Processing:
Consignment Stock Processing
Purpose
Consignment goods are goods which are stored at the customer location but which are owned by the company. The customer is not obliged to pay for these goods until they remove them from consignment stock. Otherwise, the customer can usually return consignment goods that are not required.
Consignment Fill-Up: Consignment fill-up replenishes the stock at the customer site. Since the goods remain the property of the company, this process is not relevant for pricing and consequently not for invoicing either.
Create a sales order using order type KB.
Enter the required data on the customer, the consignment goods and the delivering plant.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The underlying goods movement type is a stock transfer. This ensures that when goods issue is posted, consignment special stock is created for the customer concerned. If special stock of this kind already exists in the delivering plant for this customer, the goods are posted to this special stock.
Order type: KB (document category C: sales order)
Std. Delivery type: LF
Item category: KBN (not relevant for pricing and billing)
Schedule line category: E1 (relevant for deliveries, uses availability check, 631 (GI consignment: lending) to post the stock into a special consignment category in the delivering plants stock for that particular customer and material)
Copy control rules for the sales doc, item category, and schedule line category.
Use trans MB58 or MMBE to check the stock.
Consignment Issue: The Consignment issue enables the customer to withdraw consignment goods from the special stock that are to be used or sold.
Create a sales order using order type KE.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a delivery as the subsequent document for this sales order and, after picking has been completed successfully, post goods issue.
The goods are then reduced by the relevant quantity in the special stock assigned to the customer. This goods issue also reduces your total stock.
Invoice the delivery which issues the consignment goods.
Order type: KE (document category C: sales order)
Std. Delivery type: LF
Invoice: F2
Item category: KEN (relevant for pricing and deliver related billing, special stock indicator W, should determine cost too)
Schedule line category: C1 (relevant for deliveries, uses availability check, 633 (GI issue: customer consignment)
Consignment returns: proceed as follows: Consignment returns enable your customer to return goods to the consignment stock that has already been issued from it.
Create a sales order using sales order type CR.
Enter the required data on the customer and the consignment goods.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The goods issue posting cancels the goods issue posting which was carried out when the consignment goods were issued. This posting records the return of the goods to the plant where goods receipt was carried out.
Create a credit memo for the consignment return you created in Step 1.
Order type: KR (document category H: returns)
Delivery type: LR
Credit for Returns Order type: RE (delivery or order related billing)
Item category: KRN (relevant for pricing and deliver related billing, special stock indicator W
Schedule line category: D0 (relevant for deliveries, no availability check, 634
Consignment Pick-Up: The company uses consignment pick-up to take back consignment goods that are faulty or excess materials that the customer does not need. This process is not relevant for billing since the goods remain the property of the company.
It may be beneficial to have a mandatory reference such as the consignment fill-up. In addition to it copy control rules can be used to further control it. In the copy control rules indicate the document flow. As the stock is coming back into the warehouse or plant, you can specify a returns shipping point to be automatically determined. No invoice is necessary, as the goods are not changing ownership.
Create a sales order using order type KA.
Enter the required data for the customer, the consignment goods and the plant to which the goods are to be returned.
Enter all other relevant data and save the order.
Create a returns delivery for the sales order (the system automatically chooses delivery type LR). The transaction is completed by the goods issue posting which initiates a transfer posting from the customer's special stock to your plant stock.
Order type: KA (document category C: sales order)
Delivery type: LR
No invoice
Item category: KAN
Schedule line category: F1 (relevant for deliveries, availability check against the stock on the customers consignment, 632 (Consignment pickup)
Contracts
Contracts represent special business relationships with customers based upon material, price, and qty. They guarantee a special price agreement with the customer and are usually called outline agreements in std SAP terminology.
There are four different types of contracts provided by SAP. They are:
1) Quantity contracts
2) Value contracts
3) Service and maintenance contracts
4) Master contracts
Regards,
Rajesh Banka

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Business Flow for Down payment

Dear All,
1. when and where Down payment will appear in FI business flow
2. what are the process will happend in down payment.
3. What is the end stage of down payment.(Vendor & Customer)
Can i have Business Flow digram for Down payment to vendor and Down payment from customer (Visio or Aris)
My mail id : [email protected]
Thanks

Hi Down payment is handled in the following manner
Plz assign points as a way of thanking
Down payment 3000
Final Invoice 10,000
Transaction:
Invoice to Customer for Down payment: F-37. This is a noted item and there is only one line item in the document. If you want to handle this thru SD, then you should ask SD consultant to configure a billing plan in the sales order.
Noted item 3000
When you receive the check from the customer F-29 and you can clear the open down payment request.
Dr. Bank 3000
Cr. Customer (special gl indicator A) 3000
When you finally bill the customer for full invoice,
Dr. Customer 10000
Cr Revenue 10000
Clear Down payment:
F-32, clears the 3000 against 10000 and makes the open item 7000.
Final payment form customer 7000
Dr. Bank 7000
Cr. Customer 7000

Business One T-Installation and Contract differences

Dear All,
What are the differences between Business One T-Installation and Contract ? Where could I find the file explain about it ?
TIA
Rgd,
Steve

I am sure that there is no specific different that will give bad influence for the customers of SAP B1.
I suggest you to ask the sales or marketing dept. It seems that they could know it more detail about it or asking SAP support can also be helpful
Rgds,

Sales trading contract process

I want to test the scenario for Sales trading contract.
Please let me know the steps. We use tcode WTEW.
In sales order flow I see delivery,GD goods issue & Invoice.

I have created outbound delivery via TEW from sales order.
Then I want to do PGI of the delivery but when I want to do it though vl02n.
I am getting error that document 123453642321 can be only changed through TEW.
How I can I do the PGI of this delivery.
in task under step I choose billing & I give delivery no. asuming that at this time pgi and billing will be done but after clicking on F8
I see select source document where it shows lines as blank.

Can we use same Business Service for Sender and Receiver

Can we use same Business Service for Sender and Receiver

Hi
In addition to the above infomation explaining about the Business Service..
Business Service: Address an abstract business entity as the sender or receiver of messages.
Using a business service, you can define the technical or business subunits of the companies involved and then assign them the relevant interfaces.
The business services are used when configuring cross-company processes also..
regards
Kishore

Handling Business Area for sales documents

Hi Experts,
My requirement is that , I have to change the default Business area , determined by the system , at the time of sales document creation . For Eg: I have two business areas 0001 and 0002.
When i create a sales document , by default system determined business area 0001. But if certain conditions are met , i have to change the business area to 0002. and finally when we post the document to the Accounting after billing , the document must hit the business area 0002.I could able to change the business area in the sales documents through the user-exits available for Delivery document and Billing document .But when i post the document into accounting , the entries are going into wrong business area . How to handle this situation.
Thanx in advance.
Durga.

You mean there is a different business area in sales and account document after creation? Are you sure?
Or your user exits might not be updating properly? else system might be re-defining business area in accounting thru configuration.
Regds
Manohar

HOW TO CALCULATE NET SALES AND CONTRACT PRICE?

Dear experts,
I have the requirement of sales price report
the report layout should be
Prod descr material Number Contract type contrcat name rebate net sales contract price units
we have the master data information is reside already in multiprovider and transaction information how to calculate in frond end ?
for sales pricing report how to manipulate teh net sales and contract price
value?
any standard formulaes is there?
plz suggest me
regards

Hi,
For quick and best response unless someone answer's in this forum, post your question in SAP Community Network Forums » SAP Solutions » ERP - Sales and Distribution (SD) General or something related to your question.
Check this link if it helps -
http://help.sap.com/saphelp_46c/helpdata/en/93/74353e546011d1a7020000e829fd11/frameset.htm
Thanks,
Shambhu.

Business package for PM and SD

hi,
I am looking for Business package for PM and SD . we are on Netweaver 7.0(2004s), Portal 7.0 and ECC.
I tried to depoloy "Business Package for Sales " Release 60.1 but its not showing up in my PCD.
please share some knowledge.
Regards
stan

If u have correctly deployed Business package using JSPM means it wil show defeintely show in PCD
goto content admin -- portal content -- content provided by sap -- specalist -- here u can see ur BP
and also see SAP Note:731386
Regards
Krishna.

Business Package for Sales in SAP R/3 4.6C

Is it also possible to use some of the functions of the Business Package for Sales for connecting to an SAP system 4.6C? I want to use the standard ITS webgui and hope there are some developed templates which I can use.
Best Regards,
Alvaro

-> 46C is no longer in standard maintenance (you could order extended maintenance at an extra price...)
-> so: you either order or you will not be able to dl r/3 46C
-> which database system do you plan to use?
-> i'd rather start with sap r/3 47x200 sr1 or sap erp
standard installation procedure:
- get instguide + relevant sapnotes
- check & apply prerequisites
- as for oracle: install database software oracle (using runInstaller) and apply patches
- install central instenace using r3setup and template r3central.r3s
- install database instance usind r3setup and template r3database.r3s
- perform post-installation actions..
GreetZ, AH

Business Package for Sales or Internet Sales

Hello: I am looking for people that have experience working with Business Packages for Sales 60.1. I believe this is the only package that supports "Internet Sales" scenarios but it requires an ECC 5.0 backend, so I want to find out if the iviews within contain only sapgui or BAPI calls or BSPs or something else like webdynpro or ITS? I am also wondering if anybody has seen this pacakge work for connecting back to a 472 R/3 backend?
Thank
George

Hello again,
This is what i did:
I unzipped the SCA-File and found an EPA-File.
I imported the EPA-File with the Enterprise Portal:
SystemAdministration>>Transport>>Import
Everything looks OK.
Hope I did the right thing - other opinions?
Christoph

Business Flows for Sales and Contracts process

Similar Messages

Maybe you are looking for