Regd creation of New Sales Order Type - Credit Memo Request

Hello Gurus,
I have created a New Sales Order Type as per the given requirements. This is a Credit Memo Request. I have done all that are needed from SD perspective.
Can you please let me know what needs to be done from FI-CO perspective when a New Sales Order Type is created and this is a Credit Memo Request. If some one can let me know the customizations that needs to be done it will be very helpful for me.
Thanks,
SNK.

Hi,
As per my understanding, there is nothing to be required from FI-CO perspective, in case when you defined a document type in SD.
During the sales order processing the SD-FI interface happenes for following activities
1) Credit check (In case you use Credt management)
2) Tax determination
For more knowledge
go through the link given below.
http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
Hope it helps,
Regards,
MT

Similar Messages

Blocking creation of particular sales order type

HI ,
I initially my sales order type was ZMF , so many sales order are open , as of now I want to block the creation one new sales order of type ZMF,
Please guide me

Hi Sunaina,
Simply go to the details of ur doc. type (i.e in Define Sales Doc. types in SPRO) & put "X" in the "Sales Document Block" field on the top right of the order type.
This will block d usage of this particlar doc type.
Hope it helps. Plz close the thread if answered.
regards

IMG Settings for creating a new sales order type

Hello All,
I seek you valuable inputs on the steps to follow in IMG(SPRO) setting to create a new sales order type in the system.
I want to create a new sales order type for which i have done the following setting in IMG,
1) Sales and Distribution->Sales->Sales Document Header->Define sales document type.
2) Sales and Distribution->Sales->sales Document Header->Assign Sales Area To Sales Document Types.
3) Sales and Distribution->Sales->Sales Document Item->Define Items Categories
4) Sales and Distribution->Sales->Sales Document Item->Assign Item categories
5) Sales and Distribution->SalesàSchedule Lines->Assign Schedule lines Categories.
Also created a new number range for the same.
After this when i am trying to create a sales order with VA01 i get an error "Enter a Sales Area".
what am i missing ?Please suggest.
Thanks in advance,
Swati

Hello,
In the Initial screen of VA01 you have to enter the sale area which is nothing but the combination of
Sales organization
Distribtion channgel
Division
And in the transaction code OVAZ you should assign the sales document type for this sales area .
Please revert if you need any frther clarification
regards,
santosh

New Sales Order Type

Hello,
I would like to ask either it is neccessary to have a new division for new sales order type.
Thanks for your time.
Your fruitful answer will help me to move one step forward
Sherry.

Hi,
If you created new division then you have to maintain sales area
IMG >> enterprise structure >> assignment >> SD >> assign division to sales organization and set up sales area
How is it possible for the Y109 to be assigned to the new division. How to make it default
Y109 is not assigned to division rather it can be assigned to sales area
IMG >> sd >> sales >> sales documents >> sales document header >> assign sales area to sales document type >> Assign sales order types permitted for sales areas
Kapil

Automatic Batch Determination is not happening for New Sales Order Type

Dear Experts,
I have created a new sales order type ZBPY - For Free Sales, but automatic batch detrmination and batch pick up is not happening for new sales order type, but it is activated for all the other sales order types in Production Server, can any body let me know the steps how to map this new order type to batch management and let it behave like other order types.
Thanks in Advance.
Saravanan(EKS).

Hi Saravanan,
Kindly check the following steps for automatic batch determination.
1. First check the material is maintained with batch in the warehouse management.
2. Maintain new entry for search procedure for batch determination with the new created doc type.
3. Maintain new entry for automatic batch determination for sales order or automatic batch determination for delivery ( This depends on the business process of our client, whether they want to determine the batch with sales order or at the delivery level. check this and make new entry)
4. Create Batch using T.code MSC1N with proper date of manuf. and SLED.
5. Create Batch Search Strategy using T.code VCH1 with proper strategy type.
6. Maintain stock with active batch. check this with t.code LS26 or LS24.
regards
Ravishankar M

Can't specify the customer to use a new sales order type ,why?

I created a new sales order type, finished the configeration.. but when I use it to create a order by t_code VA01 ,input the order type and sales area ,then enter, why the sold-to-party and ship-to-party are inmodifiable? i can't specify the customer... where is the problem?
appreciate you help.thank you !

Hi Sue,
I think u havent did the Partner determination for that Sales document. If you create ur own sales doc type in VOV8 ,new entries.
U need to maintain the Partner determination for that sales doc type.
this is the same,the way u maintaint the customer partner determination.
If you dont maintain this , in VA01 screen, u cant able to enter Sold to & ship to parties as it will be in display mode. I think the same error ur getting know as per ur issue.
This will def solve ur issue as i faced n overcome long back.
*reward points ,if helpful

Copy control from Sales order to Credit memo-VTAA

Hi
We have a below requirement..
While copying from sales order to Credit memo order type,defualt payment terms in credit memo order type should be always change to NT00(payable immdtly due date)
So we had written a routine under sales order copying .VOFM-901
In VTAA we have set 901 instead of 101 under Copying requirements for transferring business data-under change header view..
But while creating sales order type CR with reference to normal sales order,it is not copying the NT00 payment term..
Can u tell us whether any other settings required in VTAA.
Note:We had copied existing 101 to 901 with addition logic -
IF VBAK-AUART = 'CR'.
VBKD-ZTERM = 'NT00'.
ENDIF.
Regards
Sudha

Hi Sudha,
The coding added in 101 is not enough to achieve your requirement, because of the fact that the VBKD-ZTERM will be filled again with the original value from CVBKD in the copy routine on the item level. (For example 102 for OR to OR in standard system)
Could you please create another routine 902(adding the addition coding to 102) and replace it on copy control for item level?
It should work then.
Regards,
Smile

Creation of new Sales order

Hi,
       While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

Number range creation for new service order type

Hi,
Could anyone please tell me how can we create service order number range if we have done a new service order type creation, and what should we do: should we create the number range in development and then transport it to the production or we should directly create it in production.
Thanks and Regards

HI,
You just define number range in tcode VN01, but remember that number ranges are not transportable.
Once you define number ranges in development, do the same in quality & production client.
Then attach number ranges in document type & transport this config to quality & production
Please see that before transportating, the number ranges must have been created in quality & production thru VN01.
Hope this helps you
Regards
Dhananjay

Should we create new sales order type for Brazil

Hi,
We are having SAP Global templete environment & going for Brazil rollout. My question is whether we can have exitsing sales order type or should we create a new one so as to capture complicated Nota fiscal requirements.
What SAP recemmends
Thanks
Amb

Most of the sales document types for Brazil are identified by BR in the description, for instance, sales document type ORB for Standard Order BR. This means a separate order type.
[Country version Brazil exclusively deals with Nota Fiscais.|http://help.sap.com/erp2005_ehp_04/helpdata/EN/10/e0f0371bc15d73e10000009b38f8cf/content.htm]

Change price sign during copy from Sales order to credit memo

Dear All,
due to external system reasons we I need to manage one sales order type using not necessarily positive amounts.
A custom logic (based on structural elements, tax information and sign of the amount) permits to identify the right billing type document to use.
Example (using a simplified logic) if the amount is positive the custom logic will determine an invoice.
and if the amount is negative a credit memo.
In VTFA copy rules has been defined but it seem that using transfer rules at item level (defined on VOFM) it is not possible to access and change the sign of the amount (net price will be enough) in order to have a negative amount copied into a positive amount of a credit memo.
The following test has been done without succeed:
custom routine on VOFM to change sign of VBRP-NETWR...but the price is 0 when the routine is called
Using pricing type M - No effect
Every hint will be highly appreciated.
Regards

Hi Sudha,
The coding added in 101 is not enough to achieve your requirement, because of the fact that the VBKD-ZTERM will be filled again with the original value from CVBKD in the copy routine on the item level. (For example 102 for OR to OR in standard system)
Could you please create another routine 902(adding the addition coding to 102) and replace it on copy control for item level?
It should work then.
Regards,
Smile

Different tax codes for a Sales order and Credit memo

Dear All,
We have created a sales order and in the invoice some X Tax code is determined in the Account document.
But when we created a Credit memo request with reference to the same Sales order, we are getting different tax code in the Accounting document of Credit Memo.
Kindly clarify how is it possible.
Regards,
Mullairaja

HI
Credit memo request with reference to the same Sales order
Because Suppose
Case 1 : you created Sale order 100 PC & Delivery 50 PC, Invoice raised 50 PC
In that above case if you take Sale order reference system will take 100 PC , but logically you need to raise Credit memo for 50 PC
Like that we can create Some cases , so try to create credit memo request based on Invoice not for based on Sale order number
Coming to you Query , try to check the Ship to party for that line item and also check the master data's once
I hope you understand
Regards,
Prasanna

New pricing procedure for Credit memo request

Hi All,
I used pricing procedure ABC01 for sales and billing.
I want to use new pricing procedure ( ABCO2) at the time of creating credit memo request, this credit memo req is with reference to Billing document.
If I dont use with ref to billing document I can able to create credit mem req with pricing procedure ABC02,
but if I am trying to create credit mem req with ref to billing document the pricing procedure in the billing document is being picked which is ABCO1.
Can any one suggest where I am doing wrong.
I maintained all the relevant copy controls.
Thanks & Regads
BVDV

Hi
Assign Document pricing procedure Z in VOV8 for CR document type , Now do the pricing procedure determination in OVKK with sales area + Cupp+Dupp=new pricing procedure
Example :
In OVKK, determine with 1000 + 10+ 10 + A+ 1 = standard pricing procedure for normal sales
For credit memo in OVKK determine with 1000 + 10+ 10 + Z+ 1 = New pricing procedure for Credit memo
Then when you create a sales order (with document type CR ) with reference to billing document then the new pricing procedure will get copied.
Regards
Srinath

Return order and credit memo request

Hi SD guru,
If goods returned by the customer then what is the appropriate sales order type i should use means whether i have to create the credit memo request or return sales.
Please elaborate both scenarios where exactly i can use sales order type return and credit memo request.
Thanks
saj

hi sajid
when ur creating the Return order use the doc type RE in standard
followed by return delivery LR adn billing ths nothing but the creditmemo.
if your supposed to just adjust the values . then use the G2 credit memo request , with reference to the billing doc for which ur intending to issue the credit memo,and credit memo by billing the same .
hope this answers your question
reward if helped
regards
giri

How to create new line item in credit memo request in rebate settlement

HI friends,
I need aimmediate help on following.
Requirenment is for given agreement all invoices for that needs to be retrieved. In those invoices we need to check the tax code or tax city for all invoices. If all are same then do nothing.
But if any of these 2 fields are different in all retrieved invoices, then we need to sum up the qty for all invoices having same tax code/city & like wise ned to create a credit memo request which will have one line item for each tax code/city.
Example:
Agreement 9999 with the relevant sales volume:
Invoice 1: Material A, tax key X, quantity 1 kg
Invoice 2: Material B, tax key X, quantity 2 kg
Invioce 3: Material C, tax key Z, quantity 4 kg
The credit memo request for agreement 9999 should look as such:
Thanks & regards,
Abhijeet.
Item line 1: SETTLEMENT MATERIAL, tax key X, 3 kg
Item line 2: SETTLEMENT MATERIAL, tax key Z, 4 kg
Please help me . I am not getting the user exit / badi for this development.
Please let me know if any one of you know from where to do this?

Hi Vinod,
The relationship with main item is stored with CRMD_ORDERADM_I- Parent.
You need to pass the guid of main item to orderadm_i-parent. This will keep the relationship with main item.
Thanks
Ajay

Regd creation of New Sales Order Type - Credit Memo Request

Similar Messages

Maybe you are looking for