What is the Purpose of Internal Sales Order in OM

Hello All,
Compared to normal Inter-Organization Transfer (Direct&In transit) in which business scenario, Internal Sales Order(ISO) Cycle would fit ? (In Manufacturing , Distribution etc.,)
what is the (main) purpose of going for Internal Requisition (IR) - ISO ? & usage of Transfer Credit account in Inter-Org Transfer?
Please share your implementation experience ?
(if any)
Thanks, Jay

The most important 1st thought is ::
Ques 1. Why ISO over Direct-Org transfer ?
Ans ---- Direct-Org transfer is immediate 2-way txns where ... there is no concept of In-transit Inventory & its tracking(s).
Source-Org Sub-inventory ~ issues out
Dest'n-Org Sub-inventory ~ receives in
which is very much like Sub-inventory transfers with the difference that its Inter-Org
Ques 2. What is this concept of In-transit Inventory ~ Inter-Org transfer v/s ISO ?
Ans ---- Yes both ( Inter-Org transfer or ISO ) have this concept of In-transit inventory & its tracking(s).
Ques 3. Now the question is -- Why then ISO over Inter-Org transfer ? How ISO rules above Inter-Org transfer ?
Ans ---- ISO is requisition based. Now using which we can have booked Sales-Order.
Using their desirable shipping dates Planning, Replenishment & Reservations can be done. You just cannot do this Inter-Org transfer.
Also the cost-price of Source-Org goes into the Dest'n-Org. Whereas in ISO you have both provision same cost price our using price-lists / modifiers ?
No doubt !! ISO is very scalable route.
Other technical reasons :: feel free to communicate ::
Ajay Kuma
c510-456-5322

Similar Messages

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

What is the purpose of using rush order doc type?

what is the purpose of using rush order doc type?

hi,
In a rush order transaction, the customer picks up the goods or you deliver the goods on the same day as the order is placed. In the standard system, when you save this sales document type, a delivery is automatically created and billing is related to the delivery.
In the standard system, sales document type SO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted.
Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
CHAN

What are the tables corresponding to sales order - parners

Hi Folks,
Can u pls let me know what are the corresponding tables n fileds for the va02->parners i.e sold to party, ship to party etc, buyer , bill to party and contact details , adress of these parners wil store.
Thanks in advance.
Regards
Rajesh

hii i am sending u the full code thta i had designed for my sales order confirmation using sap script
TABLES: VBAK,
        ADRC,
        VBPA,
        VBAP,
        SPELL.
DATA: BEGIN OF TVBAK OCCURS 0,
      VBELN LIKE VBAK-VBELN,
      AUDAT LIKE VBAK-AUDAT,
      KUNNR LIKE VBAK-KUNNR,
      VKORG like VBAK-VKORG,
      END OF TVBAK.
DATA: BEGIN OF TADRC OCCURS 0,
      ADDRNUMBER LIKE ADRC-ADDRNUMBER,
      NAME1 LIKE ADRC-NAME1,
      NAME2 LIKE ADRC-NAME2,
      CITY1 LIKE ADRC-CITY1,
      POST_CODE1 LIKE ADRC-POST_CODE1,
      COUNTRY LIKE ADRC-COUNTRY,
      KUNNR LIKE VBPA-KUNNR,
      VBELN LIKE VBPA-VBELN,
      END OF TADRC.
DATA:BEGIN OF TVBPA OCCURS 0,
     ADRNR LIKE VBPA-ADRNR,
     KUNNR LIKE VBPA-KUNNR,
     VBELN LIKE VBPA-VBELN,
     END OF TVBPA.
DATA: BEGIN OF TVBAP OCCURS 0,
      POSNR LIKE VBAP-POSNR,
      VBELN LIKE VBAP-VBELN,
      MATNR LIKE VBAP-MATNR,
      ARKTX LIKE VBAP-ARKTX,
      KWMENG LIKE VBAP-KWMENG,
      VRKME LIKE VBAP-VRKME,
      NETWR LIKE VBAP-NETWR,
      WAERK LIKE VBAP-WAERK,
      END OF TVBAP.
DATA :W_VBELN LIKE VBAK-VBELN,
      s_amount like vbap-netwr ,
      amount_word LIKE SPELL.
selection-screen: begin of block b1.
select-options: s_vbeln for vbpa-vbeln no intervals no-extension.
selection-screen: end of block b1.
*AT SELECTION-SCREEN.
SELECT VBELN INTO W_VBELN FROM VBAK
      WHERE VBELN IN S_VBELN.
*ENDSELECT.
START-OF-SELECTION.
SELECT VBELN AUDAT KUNNR VKORG FROM VBAK INTO CORRESPONDING
FIELDS OF
TABLE TVBAK WHERE VBELN IN
S_VBELN.
   IF SY-SUBRC <> 0.
     MESSAGE I398(00) WITH 'NO DATA'.
   ENDIF.
SELECT NAME1 NAME2 CITY1 POST_CODE1 COUNTRY FROM ADRC INTO
CORRESPONDING
FIELDS OF
TABLE TADRC.
   IF SY-SUBRC <> 0.
     MESSAGE I398(00) WITH 'NO DATA1'.
   ENDIF.
SELECT ADRNR KUNNR VBELN FROM VBPA INTO CORRESPONDING
FIELDS OF
TABLE TVBPA WHERE PARVW = 'WE'.
   IF SY-SUBRC <> 0.
     MESSAGE I398(00) WITH 'NO DATA2'.
   ENDIF.
SELECT VBELN POSNR MATNR ARKTX KWMENG VRKME NETWR WAERK FROM VBAP INTO
CORRESPONDING
FIELDS OF TABLE TVBAP WHERE VBELN IN
S_VBELN.
IF SY-SUBRC <> 0.
   MESSAGE I398(00) WITH 'NO DATA3'.
   ENDIF.
LOOP AT TADRC.
   READ TABLE TVBPA WITH KEY ADRNR = TADRC-ADDRNUMBER.
      IF SY-SUBRC = 0.
       MOVE TVBPA-KUNNR TO TADRC-KUNNR.
       MOVE TVBPA-VBELN TO TADRC-VBELN.
       MODIFY TADRC.
      ENDIF.
ENDLOOP.
****reward if helpfull ******

What is the maximum lines in sales order

hello friends,
what is the maximum lines that we can create in a single sales order?
how about in a sales invoice, how many is the maximum lines?
thanks!

There is no limit on the sales order lines, we do have 1800 to 2000 lines sales orders in our system.
But the AR side the defult value for the Profile option AR: Maximum Lines is 100k, if you anticipate more lines than 100k for each invoice run then you have to modify the profile option.
Srini C

What are the steps to send sales order custom field from CRM to ECC

Hi Xperts,
We have created a custom field in sales order [ VBAK] and successfully replicate its value from ECC to CRM. But while doing the enhancement to replicate the field value from CRM to ECC [ When the SO is created in CRM ] we are not able to do so.
We used a FM in CRM0_300, but while replicating the SO from CRM to R/3 it is not getting called.
Please help us by providing the steps to do the full enhancement to replicate the custom field of SO from CRM to ECC.
Thanks in Advance.

Hi Anjaneyulu,
We are faced with a similar situation as you.
Here is our scenario with the steps that we performed so far:
1. We have added a few custom fields in CRM 7.0 (Ehp1) using AET.
The BDoc BUS_TRANS_MSG has been automatically extended with these custom fields.
2. On ECC side also, same custom fields have been added to VBAK and VBAP, using APPEND STRUCTURE. Fields were added to ADDITIONAL DATA TAB B in VA01 / VA02 transactions.
3. Extended BAPI structures BAPISDITM and BAPISDITMX in both CRM and R/3 Side.
4. As mentioned in the note 1053817, we have implemented BADI CRM_DATAEXCHG_BADI -> Method CRM_DATAEXCH_AFTER_BAPI_FILL in CRM (mapped fields from BDOC to BAPI structures)
5. In the above note, for R/3 BAPI to R/3 API they have given to implement user exit USEREXIT_MOVE_FIELD_TO_VBAP which we found in MV45AFZZ. But in this we are unable to find BAPI Structure to map.
Our issue is, when a sales order is created in CRM, it is getting replicated on ECC. But, only standard fields are getting replicated. The custom fields that we have added are remaining empty on ECC side.
In CRM --> txn SMW01, we can see that the BDOC is populated with custom fields also.
Could you let us know if your issue is solved completely. Are you able to see the value of custom field, in ECC? Did you use AET to add fields in CRM.
Could you please give us the steps that you have done.

Internal sales orders commission

Hi
Any one tell me what is the use of Internal sales orders commission because i have seen so many Links all are talking about Sales order s which belong to Out side .. But i want to know what is exact business process where we can implement..
Any one tell me any separate configuration process For Internal sales order commission

Dear Raghu,
Thanks for the Link We are also facing the same scenerio to be configured. I want to understand that in the Cross System Inter company code stock transfer...
APO comes into picture, I do not have knoledge of APO so how will I be able to configure the same in existing R/3 system?
We are using the ECC 6.0
regards,
Amlan Sarkar

Internal Sales order Status should remain Entered

Internal Sales order Status should remain Entered.
Here it is automatically getting BOOKED
1) I have created one PR -100
2) Approved it
3) Ran create internal orders
4) Login as Order Management responsibility.
5) Import orders
6) Searched for the ISO -200.
7) It’s status is in BOOKED
We want the status of Internal sales order to remain = Entered.
So that changes can be made to the sales order.
Is there any profile options?

Hello,
I realize this is an old thread but it is exactly what I have encountered.
I am able to import an internal Sales Order with a Status of Entered. However, I need to import these orders with a Status of Booked (we have no process for Booking Internal Sales Orders).
We are on 11.5.10.2 EBS on 10.2.0.4 DB.
We have multiple inventory orgs but we have only processed Internal order between two of them P Org to F Org. those internal Sales orders are imported with a Status of Booked.
However we need to have Internal Sales Order from P Org to N Org. When I import these internal Sales Orders they import with a Status of Entered.
As it works as expected in one Org but not the other, I believe it must be a Org setup issue.
Any suggestions on where to look?

Tcode for displaying the changes made to sales order

hi,
i want to know is dere any tcode which displays how many times and by whom and what are the changes made to sales order.

hiii
use VA03 for display..
also refer to following link
Regarding 'display of changes in the sales order'.
regards
twinkal

What is the purpose of using cash sales doc type?

what is the purpose of using cash sales doc type?

You can go through the link
http://help.sap.com/saphelp_46c/helpdata/en/70/a7853478616434e10000009b38f83b/frameset.htm
Update from help.sap.com
Cash sales is an order type for when the customer orders, picks up and pays for the goods immediately. The delivery is processed as soon as the order has been entered. A cash invoice can be printed immediately from the order and billing is related to the order. Receivables do not occur for the customer as they do for rush or standard orders, because the invoice amount is posted directly to a cash account.
Process Flow
In the standard system, sales document type BV is saved for cash sales with immediate delivery type BV.
When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing. Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer.
The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type BV.
If the customer has already received the goods, this delivery should not be relevant for picking. If the customer is to pick the goods up from a warehouse, the delivery should be relevant for picking. If the goods are to be sent, this can be processed by maintaining the delivery in the usual way.
The system automatically creates a resource-related billing index which updates the billing due list. Billing document BV is created as the system processes the billing due list, but an invoice is not printed.
Once the customer has received the goods and is satisfied with them, the transaction is considered to be complete. We recommend that you post goods issue in the background using a program designed specifically for this purpose. You can then bill the transaction.
The cash sale can only be billed if the order quantity is the same as the goods issue quantity. If this is not the case, you need to adjust the cash sale document so that the delivered quantity and the quantity to be billed match.
You use an order-related collective billing process to bill the cash sale, but an invoice is not printed. The sales order number is used as the reference for the accounting document, created in Financial Accounting.
Dealing with Problems and Complaints
If the transaction does not run smoothly, manual intervention is necessary. For example, if the required quantity of goods is not found in the warehouse, you need to adjust the delivery quantity. Equally, if the customer is not prepared to pay the agreed price, because, for example, the goods are scratched, you can change the price in the cash sale document.
In extreme cases, you can delete the entire transaction, starting with the delivery.
If the delivery is damaged before it is picked up but after it is paid for and there is no replacement stock, you can initiate a subsequent delivery.
If you make changes to the cash sale, you can issue a new cash sale invoice using the repeat printout function.
Creating a Cash Sale
In the initial screen, choose Logistics ® Sales and distribution ® Sales.
Choose Order ® Create.
Enter the order type for cash sales (BV in the standard system) and, if necessary, the organizational data.
The values for sales organization, distribution channel and the division are usually proposed from user-defined parameters. Entries for the sales office and the sales group are optional.
Choose Enter.
Enter the following data:
Customer number of the sold-to party
Material numbers
Order quantities for the materials
Choose Enter.
If the system carries out an availability check and finds that there is insufficient stock for an order item to be delivered on the requested date, it displays a screen on which you can choose between several delivery proposals. Normally, in a cash sale, you only sell the quantity you can deliver on the spot.
Save your document.
The system automatically processes the delivery in the background and prints out a cash sale invoice. The amount of the sale is processed later in an order-related billing transaction. The amount is posted to financial accounting, using the order number as reference. Because this is a cash sale, no invoice is produced during the billing run.

What is the purpose of using return process sales doc type?

what is the purpose of using return process sales doc type?

hi,
There is the standard process
1)Order type( RE) VA01
2)Delivery( LR)Vl01n with reference to return order
i)if the movement is 651then system will not generate accounting document upon doing Post goods Receipt ,the stock will be in the return location
then you use movement type 453 to get the stock in UN restricted
ii)if the movement type 653 the system generates accounting document and stock posts in unrestricted use
3)With reference to Delivery raise Credit memo (RE) with transaction VF01
CHAN

What is the purpose of using debit process sales doc type?

what is the purpose of using debit process sales doc type?

hi,
A debit memo is a transaction that reduces Amounts Payable to a vendor because; you send damaged goods back to your vendor.
Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is like a standard order. The system uses the debit memo request to create a debit memo.
CHAN

Issue with the Internal sales Order

Hi
We are trying to populate the customer information in the internal sales orders.
We are updating the Customer_ID, Customer_Number, Customer_name information on the iface header table...and we are submitting the Order Import concurrent program...even though customer information is not populated....
Could any one sggest on this....
Regards,
Krishna

Why are you updating the interface record?
You create and approve an internal requisition (IR)
You run the "Create Internal Orders" concurrent program.
This program reads the IR details and populates the Order Interface table.
Then you run the "Import Orders" concurrent request.
That program processes the interface record and creates the Internal Sales Order (ISO). All the information Oracle needs to create the ISO (such as customer name, number etc.) is already in the interface table or is derived by the Import Orders program. You should NOT update the information.
Hope this helps,
Sandeep Gandhi

What is the purpose of using credit process sales doc type?

what is the purpose of using credit process sales doc type?

hi,
A transaction that reduces Amounts Receivable from a customer is a credit memo.
Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the block. The system uses the credit memo request to create a credit memo.
CHAN

Internal Sales Order vs. Stock Transport Order

Our company (SAP ECC 6.0) currently uses STO's to transfer finished product from Mills to Distribution centers in various regions. However, much of these Stock Transfer Orders are done for the purpose of Sales and thus our Sales assoiciates are entering these orders in the purchasing module.   These associates spend all thier time in a custom sales screens created for them and really don't like to go do the STO's in another place and try and manage them when they are not used to seeing things differently.
The Sales business has equested that we look into using Internal Sales Orders (& some sort of automated PO's on the other side) to transfer this material and for those plants to get Sales credit back for this material. They really would like to see Invoices for these sales as well (which they don't with STO's).
I would like to know everyone's opinion on using a Internal Sales Order/PO vs using a STO to transfer this product?   What Pros & Cons do you see and is it even possible to replace the STO's with Internal Sales Orders/PO's? Thanks for your input!

The people entring the STO currently are all Sales associates who only want to deal with the sales module and not the purchasing module.   From a Sales perspective, they would also like to see invoices - they don't see invoices today with STO's. They would like to do internal Sales Orders as opposed to STO's. They've ask us to do analysis on what this would take.   We have been looking at creating the Internal Sales (ISO) and then doing some sort of subsequent "NB" Purchase Order.
They're are several missing parts/questions that have come up with this research on doing ISO's / PO's vs STO's;
(1) Stock in Transit - how is it tracked?
(2) Auto generation of the PO from the ISO - system thinks the PO should come first if doing internal orders - however in our case demand comes in from many different sources and business would like to enter ISO first and then generate subsequent PO to receive against?
(3) ATP - not "double-dipping" ATP from both Sales Order and PO?
(4) Issues with invoicing (Intercompany invoicing causing a great deal of work for AP / Accounting to work through). also if no invoice is expected for PO (depending on setting up vendor as external or internal) then we'll have open accrual on the GR?
(5) Transit times in routes - when using external SO today, the date included represents the ship date with no transit times in the routesu2026STOu2019s have transit times included in their routes and its necessary for pipeline data to be complete?
Note: We have a system change request going in our system that will allow for sites to modify the price for STO's...and sites can transfer product at a negotiated rate. Our system is also set up so each individual site records these STO's as a sale...thus one of the reasons for the request above for better tracking, etc.
Thanks again for any further input you may be able to offer. Thanks!

What is the Purpose of Internal Sales Order in OM

Similar Messages

Maybe you are looking for