Double allocation for sales order

Hiii Experts,
We have manufacturing plant where we are using both make-to-stock and make-to-order strategy to fullfill the local and export demands,now as the plant is using both strategies when we create sales order and run MRP for export purpose we are getting a process order with the sales order refference so that it can confirmed and delivered to fullfil the demdands.
But since there are cases like Ex: assuming having a stock of 100 cases already available to fulfil the requirement of customer order the distrubution assign these stocks to sales order as there is no differnce in the product for local and export, through MB1B 412E movement type and delivers.and also as there is no much co-ordination between production and distribution,again the production people confirms these orders generated through MRP which is becoming a double allocation for the single sales order.
Is there any way fullfil these requirement of double allocation,please suggest so that it can be avoided....
Thanks & Regards,
sampath

Hiii mario,
Even i am not sure why the process has been following like this as i am joined a week back... will dfinately let u know the reason why they r following both stragtegies......... but can the above requirement can be fulfilled.. incase if the plant follow both startegies...?
Thanks & regards,
sampath s

Similar Messages

Stock allocation for sales orders with batch job

Hi Friends
We have a batch job to allocate stock for sales orders which runs every week , currently this batch job is meant for plant 1000 with availability check procedure Z1 .
I need to incorporate for same batch job plant 1000 with availability check procedure Z2
Just I need to know that there is any potential impact and it causes any problem ?
Thanks In Advance
Rusheek

Hi,
Check what difference is between procedure Z1 and procedure Z2. As we cant see this, you will have to analyze what Z1 was doing and what Z2 is expected to do. Broadly speaking this is preety subjective to your project.
You analyze and try to find out the impacts. If needed take help of abaper.
Rgds,
SB

How to split cost allocations for sales order lines?

Has anyone here solved a requirement to split the cost of goods sold from a service request debrief.
The scenario is -
1. A debrief of a service request is completed.
2. Material is issued and technical labor used and expenses incurred.
3. I am hearing that in Oracle Service, the material is only costed but not the technical labor and expenses.
4. No splitting can occur in any of the cases through standard Oracle?
5. We have gone down the path of creating sales order line types for each department (unique code combination) and then splitting the COGS in SLA.
6. This way, we have to create items for labor and expenses.
Is this the only semi-standard way.
Thanks for your thoughts in advance.

Hi
I have reverse the sales order settlement, PP order settlement to sales order and I have also done KB11N for transfering the cost to the new production order.
The only problem is I was unable to transfer labour hour confirmation as cost element used for this are not for transfering cost. If I will reverse the confirmation in PP order system will reverse material movement also which I don't want any more. Can you please tell me how to I reverse the Labour hours with out affecting goods movement?
Many thanks

Manual quantity allocation per sales order

Hi All,
The requirement is as follows.
My client want users to allocate quantity for sales order manually so that they can control quantity allocation for sales orders when there is shortage of stock.
We do not want to use product allocation for this, So can anyone suggest if there is any other way to allocate the stock manually for sales order.
Thanks in advance,
JM

Hi,
This can be acheived by enhancement.
You can use userexit MV45AFZB -userexit_source_determination for this.
You need to maintain the Z-table for all the bottleneck material with confirmation quatity column.
So everytime when you create a sale order for bottleneck material, system will check this table & irrespective of any order quantity, it will confirm the quantities mentioned in the table.
This way you can maintain the logic & fullfil the above requirement
thank you

Driver program for Sale Order

Hi all,
Can any body tell me Standard Driver program for Sale Order Smart form?
Useful answer will be rewarded
Thanks in advance,
Sachin.

Hi Sachin,
you can do this by,
 NACE (tocde) --> select Sales --> click output types -->
select any standard output type --> double click on processing routines.
You can see the program name
For this it is -
RVADOR01
Reply me if there is any queries

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

How settlement rule will be created for Sales order with cost object

Dear Experts,
We are using product cost by sales order with valuated stock. In addition we are not using COPA
We also consume some materials at sales order level and at the end of month we want to do the result analysis and settlement for the same amount. In this case can any on explain how system will behave regarding settlement of sales order cost and what entries will get pass in the system.
In our case we have done below activities...
we have created sales order,
All production order activities completed till final GRN including month end activities
Material consumption against sales order
Result analysis executed
At the time of sales order settlement, system throwing error (Sender doesn't have valid receiver, please create settlement rule for sender object)
Then i checked in sales order there sales order settlement rule not defined.
I guess this settlement rule need be generated by system automatically. If not, please let me know the process of it.

HI kishore
the reason is that sale order always carry the revenue and production order and production period carry the cost .
cost you can settle to the Material and even management want to be settle the cost to material only in production order OR period
but in sales order when u sell the product it carry the revenue not the cost and management want see and analysis based on profitability segment are profit center level .
Prerequisites
If CO-PA is active, the system generates a settlement rule when you create the sales order. The settlement rule determines whether data is settled to other objects or other areas in Controlling. In accordance with this settlement rule, the relevant data is settled to CO-PA.
If CO-PA is not active, create a settlement rule. This settlement rule that you create manually normally contains a G/L account as a receiver (such as 399999). You can also settle costs and revenues or results analysis data to objects with revenue.
You can also settle the cost of sales calculated in results analysis to a fixed asset or a cost center. To do this, you must add to the allocation structure the results analysis cost elements under which the cost of sales is updated to the order.
The settlement rule includes a distribution rule for the sales order item. The distribution rule is made up of a settlement receiver, a settlement share, and a settlement type:
The settlement receiver (such as profitability segment or G/L account) specifies the object to which the actual costs and revenue of the sales order item are settled. The settlement receiver can be proposed through the settlement profile.
The settlement share defines the percentage or the equivalence numbers used to distribute the costs to the individual settlement receivers. The settlement share for sales order items is usually 100%. A settlement share of 100% is preset in the system.
The settlement type specifies full settlement of the sales order item. This ensures that all the data on the sales order is available for results analysis.
Settlement still takes place in each period. The revenues and the cost of sales are transferred to CO-PA by period, and the work in process and the reserves are transferred to FI.

ATP logic for sales order and delivery

Hi experts
Generally, the ATP quantity that having in sales order ia available to other deliveries.
I wish know if batch is allocated to sales order, is it available for other deliveries? or system will not consider for delivery ATP.
warm regards
sairam

Hi,
ATP qty is generated against the Sales Order requirement. It is not assigned to other deliveries.
If Batch is assigned to Sales Order, it will not assigned to other deliveries.
Regards,

RA Category for Sales Order Actual Settlement

Hi,
During production order settlement for WIP we run in every month end. Generally in tcode OKG8 (Posting Rule in WIP calculation and Result Analysis) we use RA category WIPR(Work In Process with Requirement to Capitalize) which is used production order settlement for WIP. We have done production order settlement and successfully value posted to WIP settlement gl account because in OKG8 WIPR is maintained against P&L and B&S account. After that we have done Result Analysis for Sales Order through KKA3. Value has posted to various objects under Result /analysis. Now we need to run Actual Settlement for Sales Order. In case of Sales Order Costing what should be its RA catergory for Actual Settlment : Sales Order settlment which is run through VA88.
Best Regards,
Samrat Roy

Dear Waman,
In OKG8 posting rule WIP calculation against RA category is maintained as WIPR with P&L and BS gl account. Uner Result Analysis valuation method against RA Key for Sales Order is maintained as PREL, REL, DLV, FNBL and TECO. Production order settlement has done and value has posted to WIP gl account and Quantiy has issued for delivery and billing. After the Sale billing I have done KKA3 which is Result Analysis for Sales Order. Value has posted to Sales order wip, Actual Revenue, Actual Cost, Cost of Sale, Revenu affecting net income, Planned revenue, planned cost, Planned profit and loss value shows. After that I have run VA88 and sales order wip value has posted to wip gl accounts which is set in OKG8 both P&L and BS gl account which same gl is used for production order settlment also and I created Sales Order settlement rule which is receiver in GL accounts. That GL is external settlement GL account. That external settlment receiver gl is same as sales order settlment profile's allocation structure GL. So during final sales order settlment same gl is debited and credited of calculated profit.
But I have some doubts which I requires as per business. I need Revenue Surplus(POCS), Reserve Unrealized Cost(RUCR), Revenue in Excess Billing(POCI) and variance from Result Analysis(VARR). I wanted to set this RA category in OKG8 but system does not allow me which says alrady WIPR is maintaied and value posted to result analysis. So I need to deactivate first then new RA key can be introduced..
Also I would ask you after production order settlement for wip, shall I run wip for Sales order and Sales Order settlement. or I need to to pas customer delivery and final billing. After billing I need to run WIP on sales order and sales order settlement. Basically I will run two times WIP which are production order and sales order. Our business sceanrio consists of one sales order with 29 prouction and its corresponding 29 wip which will be finally settled to Sales order external settlment gl account.
Best Regards,
Samrat roy

Urgent: Creating ALE IDOC for SALES ORDER

hi
please tell me step by step procedure to create ALE IDOC for SALES ORDER?
reward for sure
regards
ravish

Hi,
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards

ATP check partial Quantity allocation to Sales Orders

Hi,
Our client has three different sales order types for processing sales differently for the same materials.
While doing ATP check they have a order of priority i.e ZOR1 -> ZOR2 -> ZOR3 with ZOR1 highest priority.
For sales order type ZOR2 currently they donot have partial quantity allocation to sales orders.i.e if two orders, Order 1 created with 100 Qty and other Order 2 with 50 Qty and if ATP is 50 Qty.
System is allocating material to Order 2 which has order quantity 50 ( Which equals ATP Qty )
Now the client requirement is to configure system such that it does partial allocation to Order 1 ( order qty 100, where as ATP Qty is 50 ) i.e system should allocate even partial quantity to sales orders, that too in FIFO ( system should allocate ATP qty to order created first then next and so on )
Please let me know what changes i need to do to achieve the above functionality in SAP system.
Thanks
Venkata Rama Reddy.K

Dear Venkat,
Please check the customer master for the customer which you have maintained in the 1st order. If the customer allows partial delivery, them the system will allocate the stock to the order which is created at first.
At the time of ATP check(In Availability Screen), you do need to choose, One-time or System proposal, which will allocate the stocks partially to the 1st order as you don't have enough stock.
Check out the settings in the customer master (for the customer in the 1st sale order) under Shipping Tab.
Partial delivery per item D/A/B
Max. partial deliveries >0
(And more thing, you mentioned that sales document type is having priority. As of I know - there won't be any setting which will set particular sales document type with high priority. If you are really doing that kind of setting - update the same in this forum - it may help others..)
Hope it may help you.
(Venkat: Has your issue solved? Kindly update in the forum - if your question is answered)
Thanks,
Venkatesh.S.P.

Fld selectn for mvmt type 543 / acct 2560107 differs for Sales order (013)

Dear experts,
I am trying for normal subcontracting scenario, here I have issued the material against a subcontract order with 541 movement.
Now I am trying for goods receipting,
Initially I got an error message ' Account determination for entry NGA (chart of account) GBB NG01 VBO 5010 is not possible', then I have maintained the combination in OBYC, then I tried again for posting, this time I am getting ' Fld selectn for mvmt type 543 / acct 2560107 differs for Sales order (013)'.
Can any one share your ideas, what might be the reason.
Thanks in advance,
Regards,
Krish.

Hi,
Go to Transaction SA38 - enter Program RM07CUFA and Execute
Enter Movement type 543 and Special Stock Indicator O
Enter Company code
Enter G/L account 2560107 and Execute
Under "Additional account assignments"
You can see the field "Sales order"
Click on the column "MvT" or "Accnt" as required
Now in the new screen double click on "Additional account assignments"
Change the filed selection for "Sales order" as optional and SAVE
This s to be done for both by clicking on "MvT" or "Accnt" one after one.
Now try to post Material Document

Trigering script for sales order

hello abap studs,
cud u pls tell me the procedure to trigger script for sales order..
thnx n regards,
praveen

Hi,
If the Script is ready with all the programming done for data display, then it can be associated with Sales Order using transaction 'NACE'.
Goto 'NACE'.
Select Application as 'V1'.
Press Output Types button in the application toolbar.
Select any output type which u need to associate with uir Sales Order say BA00.
Double click on Processing routines on the left.
This will give u a table in which there will be multiple output options.
In the Print output, specify ur Driver Program and the Form Layout name.
Hope this helps u.
Regards,
Himanshu

Query for Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum] ORDER BY T0.[DocNum]
where U_Total_GP is a UDF for storing the GP of each order.
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. However, the query does not calculate column total for total amount and total GP. Although I know the total for each column can be displayed by pressing "Ctrl" + Click on the column title, it would have to be done from time to time.
Therefore, I would like to modify my query in order to calculate the column totals when executed. Are there any suggestions for this?
Thank you
Regards
Elton

Hi Elton,
Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
ORDER BY T0.[DocNum]
Thanks,
Gordon

Workflow for Sales Order Release via Status Profile

Dear all,
i want to make a workflow for sales order which have 4 User Status in One status profile.
Once Event triggered for sales order
1.   Mail should go to main authority with sales order number.
2. Once authority will do some changes in the required field then he/she changes
     the user status-1 from defauts as per line Item and mail should go to department no-1 (Head authority).
3. Once again same changes in sales order but now user status-2 from user status-1
     as per line Item and mail should go to department no-2 (Head authority).
4. Once again same changes in sales order but now user status-3 from user status-2
     as per line Item and mail should go to department no-3 (Head authority).
5. Once again same changes in sales order but now user status-4 from user status-3
     as per line Item and mail should go to department no-4 (Head authority) .
and parrally for each changes of Status mail should also go to User (Event Creator).
6. Finally mail sholud go to User as you are permitted to do next business transaction for this sales order
Please tel me the process as i am very new this topic and i am always going to stuck in Binding.
please help me out.
Thank You

Hi Neeraj,
First of all start with SWELS and SWEL T-Code to check if any standard event is getting triggered or not. If event is getting triggered, then use the same event to trigger the workflow; otherwise create a custom event of BO and use the same to trigger the workflow.
Hope you are aware of T-Code SWO1 and delegation of BO. The BO used for your requirement will be BUS2000115.
As you want the workflow to get triggered only for one status profile and one of its status, so use check function module. There set the condition for you status profile and status.
The FM which you will be using the most is CRM_ORDER_READ. To read the status, you can also use CRM_STATUS_READ_OW.
Now simply make the approval steps in the workflow using activity. In the activity, you can use the standard method USERSTATUSPOPUP to send the workitem for approval. In each step use the same activity with different agents as approvers.
Just go with these things and let me know if you get stuck up somewhere.
Regards,
Guddan

Double allocation for sales order

Similar Messages

Maybe you are looking for