ALE / IDOC / sales order customer control record change

I'm trying to look for a "standard" answer. Here's my problem:
Record comes into SAP with a non-sap customer number that needs translated to SAP customer number.
Options I'm looking into:
1. Use the user exit and pull the customer characteristic from the customer master. Based on the characteristics then convert the control record.
2. Use the user exit at the sales order create. Based on the characteristics then convert the sales order and do not convert the control record.
3. Use standard EDPAR and convert the control record.
The problems:
If I use code to change the sold to custmer number at the control record level, I'd like to do the same thing at the detail level. The standard SAP code uses EDPAR. There are many different user exits based on the IDOC type in the system. I really don't want to change the code for each one.
EDPAR is maintained by IS. However, the customer master is in the business hands and is easily used. The customer master would be the perfered way to do things.
Any suggestions? Has anyone else had a problem with the customer number in the control record? We used to do it prior to moving the record into the SAP system. We would like to move away from that.
Thank you!
Michelle

OK so we have a strange setup. Yes, sold-to and ship-to is in the sales order.
The customer number in the control record is really our SAP sold-to number. It also is the partner number.   It is required for WE20. However when the IDOC comes into our system our customer doesn't always send the partner number. They can send their number for our company, the DUNS number or others. We have to take that number and convert it to our partner number.
While conversion from X12 to IDoc, based on the ISA ID or Sold-to party number you should map the correct SAP partner number onto the control record.
Coming to non-SAP sold-to party number in E1EDKA1 segment, the same non-sap sold-to number can be mapped to this segment but you should maintain EDPAR Entries. (VOE4).   Yes, I found that EDPAR seems to be the way SAP is expecting the conversions. However, we want our customer service to maintain the conversion.   That means that it has to be in a good format. So I could write a Z transaction over the EDPAR table for easier maintenance, or use the customer master screens. The customer master seems to be a logical place for custmer service to enter in the conversions. However, EDPAR is what SAP is expecting. So I decided to have them update the customer master via characteristics, and then use a BADI to send the information to EDPAR. Use "standard" functionality to change the control record. I believe it is a user exit.
Any questions?? I always have questions.   I think the above solution will work.   We haven't prototyped it yet.   That will happen soon.    My question was very generic and probably hard to follow.
Hopefully this clears up what I think we are going to do. Any other solutions would be appreciated.   The control record may or may not be correct when it is recieved. So we need to convert. Another requirement is that customer service has to set up the conversion values. VOE4 is not a good transaction for non-technical people to use.   So we need a better way.
Again we have voted to try the above solution. But I welcome any other suggestions.
Thannk you,
Michelle

Similar Messages

Recording for Purchase order,Sales order,Customer

Hi Guys,
I have done recording method for Material Master,Vendor,SE11.
I want to practice recording for Purchase order,Sales order,Customer. So can anybody give me the procedure of creating Purchase order,Sales order and Customer with values in the flat file.
Plz help me guys,
Thanks & regards,
Raj.

Hi Raj,
Here are the links for creation of purchase order, sales order and customer.
http://web.mit.edu/sapr3/windocs/bpors03m.htm
http://web.mit.edu/CAO/www/SB2002/CR/VA01.htm
http://web.mit.edu/cao/www/AR/ar1/ar_FD01.htm
Hope this will be of some help to you.
Regards,
Vicky
PS: Award points if helpful

Sales order quantity is being changed -incompletion log arising

Hi Gurus,
I come across a situation in OM.
Sales order1 is created with item 10 (qty20) on 1 may 07, delivered and invoiced.
There is a new requirement from same customer for same item. so instead of createing new SO, iam trying to change existing <b>sales order1</b>--order quantity to say 30 ( fresh reqt being 10)
when i try to deliver newly added 10 qty of item 10, iam end up with incompletion on schedule lines.
Is this correct process to edit order Qty ?
many thanks for your reply...

Hi,
Idealy speaking you should not do changes in the old order which is invoiced,insted the correct way will be to create a fresh order,delivery and billing.
this will be easy for the record purpose.Again if you dont's want to enter the same data again and agian for the same customer and material etc,you can copy the order say OR to OR.
Maintain copy control for OR to OR and sales order copy control and your problem will be solved.
Reward points if useful
Regards,
Amrish Purohit

Sales order as complete and change the delivery status.

Hello All,
We produces an order but then the customer calls and does not want the material so we in turn will scrap the material against the production order using transaction MB1A mvmt type 951 E.
Since the material were scrapped and no material were shipped against the sales order, the sales order u201Coverall statusu201D remains open and the delivery status is u201Cnot deliveredu201D.
To close the order we u201CRejected line itemu201D and moved on.
I would like to know if there is another way we can set the sales order as complete and change the delivery status.
Regards
Amit

Hello,
you can use the status profile for the same. but a better way would still be to use the rejection reasons . the rejectionr reasons are very well integrated with the document flow as well as transfer of requreiemnts to Production
so a best practise would be to use rejection reason
hope this helps
Thanks
akasha

Pop up when Sales order item partner is changed

Hi,
Can we get a pop up when a partner function in sales order item line is changed which should display the text maintained for the customer in XD02??
If so please let me know..
Thanks & regards,
Santhosh
Edited by: SS on Jun 8, 2009 3:27 PM

Hi..
Put option C there & save.
This filed defines result of ava chk in sales order.
(Rule for transferring the results of the availability check
Specifies for a particular sales area how the system reacts when the availability check determines that the inventory is insufficient to satisfy the order quantity.
Use
When inventory is insufficient, the system can react in one of two ways:
The system presents a pop-up window and you choose from different alternatives, or
The system automatically proposes one of the alternatives (no pop-up window appears)
Example
The system can, for example, automatically confirm the delivery proposal. The delivery proposal consists of the quantity that is available for delivery by the requested delivery date.)
Also make sure in OVZ8 you have ticked Av Chk for your schedule line category
Regds
MM
Edited by: MANOJ MAHAJAN on Oct 26, 2009 12:21 PM

How to save Custom control records through module pool program ?

Hi guru ,
1. How to save Custom control records through module pool program ?
I wrote multiple lines of record in custom control
Who to save that records ?
thanking you.
Regards,
Subash.

Hi,
can refer following code -
IN PAI , CODE is as follows-
*&      Form editor_output
FORM editor_output .
NARRATION1 is name of custom controller
IF v_editor IS INITIAL.
Create obejct for custom container
    CREATE OBJECT v_custom_container
      EXPORTING
        container_name              = 'NARRATION1'
      EXCEPTIONS
        cntl_error                  = 1
        cntl_system_error           = 2
        create_error                = 3
        lifetime_error              = 4
        lifetime_dynpro_dynpro_link = 5
        OTHERS                      = 6.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
Create obejct for the TextEditor control
    CREATE OBJECT v_editor
      EXPORTING
        wordwrap_mode              = cl_gui_textedit=>wordwrap_at_fixed_position
        wordwrap_position          = line_length
        wordwrap_to_linebreak_mode = cl_gui_textedit=>true
        parent                     = v_custom_container
      EXCEPTIONS
        error_cntl_create          = 1
        error_cntl_init            = 2
        error_cntl_link            = 3
        error_dp_create            = 4
        gui_type_not_supported     = 5
        OTHERS                     = 6.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
                 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
ENDIF.
ENDFORM.                    " editor_output
getting textdata in internal table as follows
*&      Form create_text
FORM create_text .
REFRESH : it_texttable,
            it_text.
IF v_doc_number IS NOT INITIAL.
    IF v_editor IS NOT INITIAL.
      CALL METHOD v_editor->get_text_as_r3table
        IMPORTING
          table                  = it_texttable
        EXCEPTIONS
          error_dp               = 1
          error_cntl_call_method = 2
          error_dp_create        = 3
          potential_data_loss    = 4
          OTHERS                 = 5.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                   WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
Now, our final text data is in internal table it_texttable.
pls, Reward if found helpful.

How to save Custom control records ?

Hi guru ,
1. How to save Custom control records module pool program ?
I wrote multiple lines of record in custom control
Who to save that records ?
thanking you.
Regards,
Subash.

REPORT ZCUSTOMC.
CLASS event_handler DEFINITION.
PUBLIC SECTION.
    METHODS: handle_f1 FOR EVENT f1 OF cl_gui_textedit
             IMPORTING sender,
             handle_f4 FOR EVENT f4 OF cl_gui_textedit
             IMPORTING sender.
ENDCLASS.
DATA: ok_code LIKE sy-ucomm,
      save_ok LIKE sy-ucomm.
DATA: init,
      container TYPE REF TO cl_gui_custom_container,
      editor    TYPE REF TO cl_gui_textedit.
DATA: event_tab TYPE cntl_simple_events,
      event     TYPE cntl_simple_event.
DATA: line(256) TYPE c,
      text_tab LIKE STANDARD TABLE OF line,
      field LIKE line.
DATA handle TYPE REF TO event_handler.
START-OF-SELECTION.
line = 'First line in TextEditControl'.
APPEND line TO text_tab.
line = '----
APPEND line TO text_tab.
line = '...'.
APPEND line TO text_tab.
CALL SCREEN 100.
MODULE status_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
IF init is initial.
    init = 'X'.
    CREATE OBJECT: container EXPORTING container_name = 'TEXTEDIT',
                   editor    EXPORTING parent = container,
                   handle.
    event-eventid = cl_gui_textedit=>event_f1.
    event-appl_event = ' '.                     "system event
    APPEND event TO event_tab.
    event-eventid = cl_gui_textedit=>event_f4.
    event-appl_event = 'X'.                     "application event
    APPEND event TO event_tab.
    CALL METHOD: editor->set_registered_events
                 EXPORTING events = event_tab.
    SET HANDLER handle->handle_f1
                handle->handle_f4 FOR editor.
ENDIF.
CALL METHOD editor->set_text_as_stream EXPORTING text = text_tab.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE user_command_0100 INPUT.
save_ok = ok_code.
CLEAR ok_code.
CASE save_ok.
    WHEN 'INSERT'.
      CALL METHOD editor->get_text_as_stream IMPORTING text = text_tab.
    WHEN 'F1'.
      MESSAGE i888(sabapdocu) WITH text-001.
    WHEN OTHERS.
      MESSAGE i888(sabapdocu) WITH text-002.
      CALL METHOD cl_gui_cfw=>dispatch.      "for application events
      MESSAGE i888(sabapdocu) WITH text-003.
ENDCASE.
SET SCREEN 100.
ENDMODULE.
CLASS event_handler IMPLEMENTATION.
METHOD handle_f1.
    DATA row TYPE i.
    MESSAGE i888(sabapdocu) WITH text-004.
    CALL METHOD sender->get_selection_pos
         IMPORTING from_line = row.
    CALL METHOD sender->get_line_text
         EXPORTING line_number = row
         IMPORTING text = field.
    CALL METHOD cl_gui_cfw=>set_new_ok_code   "raise PAI for
         EXPORTING new_code = 'F1'.           "system events
    CALL METHOD cl_gui_cfw=>flush.
ENDMETHOD.
METHOD handle_f4.
    DATA row TYPE i.
    MESSAGE i888(sabapdocu) WITH text-005.
    CALL METHOD sender->get_selection_pos
         IMPORTING from_line = row.
    CALL METHOD sender->get_line_text
         EXPORTING line_number = row
         IMPORTING text = field.
    CALL METHOD cl_gui_cfw=>flush.
ENDMETHOD.
ENDCLASS.
aniruddh

How to save Custom control records module pool program ?

Hi guru ,
1. How to save Custom control records module pool program ?
I wrote multiple lines of record in custom control
Who to save that records ?
thanking you.
Regards,
Subash.

Hi Subasha,
Please check the format below since it is based on a working code
**************data declarations
TYPES: BEGIN OF TY_EDITOR,
EDIT(254) TYPE C,
END OF TY_EDITOR.
data: int_line type table of tline with header line.
data: gw_thead like thead.
data: int_table type standard table of ty_editor.
You should create a text for uniquely identifying the text you are saving each time so that it doesn't get overwritten
For this a key combination must be decidedd to uniquely identify the test..here it is loc_nam
****************fill header..from SO10( t-code )
GW_THEAD-TDNAME = loc_nam. " unique key for the text
GW_THEAD-TDID = 'ST'. " Text ID
GW_THEAD-TDSPRAS = SY-LANGU.
GW_THEAD-TDOBJECT = 'ZXXX'. "name of the text object created
*Read Container and get data to int_table
CALL METHOD EDITOR ->GET_TEXT_AS_R3TABLE
IMPORTING
TABLE = int_table
EXCEPTIONS
ERROR_DP = 1
ERROR_CNTL_CALL_METHOD = 2
ERROR_DP_CREATE = 3
POTENTIAL_DATA_LOSS = 4
others = 5.
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
loop data from int_table and save to int_line-tdline appending it.
*save the text
CALL FUNCTION 'SAVE_TEXT'
EXPORTING
HEADER = GW_THEAD
TABLES
LINES = InT_LINE
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
OBJECT = 4
OTHERS = 5.
IF SY-SUBRC 0.
ENDIF.
The code shown above is ok and working fine for save also,hope that the above sample with helps you solve the problem
Please check and revert,
Reward if helpful
Regards
Byju

How to send IDoc(Sales Order Confirmation) without Message control

Hi,
I need to send Sales Order confirmation,Delivery and Invoice through ALE (IDoc's). I am asked not to use MESSAGE CONTROL or CUSTOM IDoc to send confimation.
I dont need to send a instant confirmation but i can do it at a specified time intervals.
Do we have any other possiblity other than the both?
Can you please give the steps to do, if possible?
Thank you in advance,
Gangolu.

Hi
This link may be useful
Re: Re-open EDI - ORDCHG for outbound sales order

Third Party process - billing date change in Sales order / Customer Invoice

Dear Friends,
In Third Party Sales Process , as we are aware billing is order related billing and it will become due only after vendor invoice is received.
               My situation is in the original sales order billing date is eg: 01.02.2009 . The subsequent vendor invoice ( Invoice receipt done based on PR --> and PO) has a later date eg: 05.02.2009 .
This means that the customer biling can be done only after this date.
How the system behaves in this case wrt to the billing date ( 01/02/2009) of the original sales order.
Regards
Mahesh
Edited by: Mahesh sap on Feb 4, 2009 8:55 AM

Hi all ,
         Thanx all for your responses . But my case is a bit peculiar . Here the vendor invoice is coming by IDoc through EDI . When EDI flow is confirmed, the billing date is pushed ahead. As per billing calendar in CMR the customer can be invoiced only on the last date of the month.
As a result if the original billing date in the sales order is Feb end, when vendor invoice received through EDI , the billing date is shifting to march end .
Is it because the date of vendor invoice is causing this? Obviously the customer billing date falls only after vendor invoice date.
Regards
Mahesh

Idoc Control record - Change to msg type not working

Hi,
We have a field in the control record that we are trying to update but it will not take. The FM is IDOC_OUTPUT_TPSDLS. Inside this FM is a call to function customer-function '020'. double click on the '020' and you go to the user exit EXIT_SAPLV56I_020.
I created the include ZXV56U30. It has one line of code - idoc_control-mescod = 'GLT'. We are trying to populate this field with 'GLT'. I activated the include and the user exit and the customer-function and finally the FM IDOC_OUTPUT_TPSDLS. The user tested and said while we are getting our custom segments populated we are not getting this idoc_control-mescod = 'GLT' to work.
What am I missing here? Do I need to do a commit after the field is populated? Is there some config that needs to be in place or what?
Any help would be apprciated since we need this by the EOD for go-live.
Thanks - many points awarded if someone can figure this out!

Hi,
Check if the user exit enhancment is added to a project in CMOD and make sure the project is activated.
Thanks,
Naren

Reg:IDOC -sales order creation

Hi All,
I am trying to create sales order through IDOCS.Basic type is SALESORDER_CREATEFROMDAT201.
My requirement is to know any user-exits where in I need to add to my code to hardstop sales order creation if the storage location which I am passing is marked for deletion.
Kindly reply as soon as possible.
Regards,
Kaveri

Hi,
Check this one it will help u how to enhance the idocs.
If we wnat to extend the idoc use the segments for adding the fields. use the tcode WE30 and we31.
Please reward points if it is useful.
Go through the following Steps For ALE/IDOC
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,
satish.

Disable Document Flow in Sales Order copy control

Hello,
We have a request where the customer doesn't want the docflow to appear when you copy a sales order to another sales order? I know that you can disable the flag for the item categories however, when you do this, there is still a link between a sales order when it's created by referencing another. Is there a way to create a sales order via "copy with reference" and to not have them linked in the docflow? Possibly one of the configuation settings in the copying control? We are on 6.0.
Thanks,
Chris

Hi,
I think It is not possible through configuration.
Pl try screen exit
or
change in standard program,which is not advisable.
Thanks,
Vrajesh
Edited by: Vrajesh G. Nayak on May 4, 2010 1:36 PM

Sales order credit control area

Hi,
How can i identify the credit control area the sales order belongs to?
Is there any way to identify in the SO itself?
(not checking the sales org and checking the cc ar)

Credit Control
Settings for determining the credit control area of a document. The settings of items 1 - 4 are taken into account according to their priority. The credit control area found is stored in field VBAK-KKBER.
1. Transaction OB38
   Check which credit control area is assigned to the company code.
   Company code:
   Credit control area:
2. Transaction OVFL
   Check which credit control area is assigned to the sales area.
   Sales area:
   Credit control area:
3. Transaction XD02 or VD02
   Check which credit control area is assigned to the payer.
   Payer:
   Credit control area:
4. Transaction SE37
   Is user exit EXIT_SAPV45K_001 being used?
5. Transaction OBZK
   For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
   OB45, or the credit control area must be entered under the relevant company code in table
   T001CM of the credit control areas allowed.
   Company code:
   Credit control areas allowed:
6. Settings for the credit checks
7. Transaction OVAK
   Which settings do exist for the sales document type used?
   Sales document:
   Check credit:
   Credit group:
8. Transaction OVAD
   Which settings do exist for the delivery type used?
   Delivery type:
   Credit group for delivery:
   Credit group for goods issue:
9. Transaction OB01
   Credit management/Change risk category
   Definition of the risk category for each credit control area. This risk category can be
   assigned to a credit account by using Transaction FD32.
10. Transaction OVA8
    Here, the individual credit checks for key fields
    o credit control area
    o risk category
    o credit group are set. Take these key fields from the above settings and go to the detail
      screen. In particular, check whether fields "Reaction" and "Status/block" are set
      correctly. To carry out follow-up actions in case of a credit block, the credit check
      status must be set (field "Status/block").
11. Transaction FD32
    Credit master data for the payer of the relevant document.
    Credit account:
    Credit limit:
    Risk category:
    Currency:
12. Settings for updating the credit values Update of the credit values is required for the limit
    check (static or dynamic credit limit check).
13. Transaction OVA7
    Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to
    field "Active receivable" in Transaction VOV7.
    Item type:
    Active receivable:
14. Transaction V/08, Pricing
    In the pricing procedure used for pricing, subtotal "A" must be entered in a line for
    determining the credit value (mark the pricing procedure and doubleclick on "Control").
    Usually, the net value plus taxes is used. This way the system is determined to use this
    subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for
    update and credit check.
    You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
    Pricing procedure:
    Line with subtotal = 'A':
15. Transaction OB45
    Which update group (field "Update") do you use in the relevant credit control area? The
    default setting is "12". If you use another update group, check whether this is fine with
    you. If you open an OSS message, please tell us the alternative update group.
    Credit control area:
    Update:
16. Transaction OMO1
    Which kind of update did you choose for structure S066?
     In any case, "Synchronous update (1)" has to be chosen as the kind of update.
     All other settings will lead to errors.
Credit Management
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
u2022 SM30 - Table/View
u2022 V_TVTW - Define Distribution Channel
u2022 V_TVTA_KKB - Assign sales area to credit control area
u2022 V_T014 - FI - Define Credit Control Area
u2022 T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
Distribution Channel
Division
Distribution Channel
Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022 Check Credit
o A - Credit limit check and warning message
o B - Credit limit check and error message (no sales order can be created)
o C - Credit limit check and delivery block (block delivery if hit credit limit)
 Options B and C -> used for checking open order values (when you create/change the sales order)
o D - Automatic credit control with open order values
 More control in transaction OVA8 - Automatic credit control
 You check for open orders and deliveries, or just open deliveries.
 or open order values with other options
u2022 Credit group
o Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022 whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022 Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022 SAP default credit groups
o 01 - credit group for sales order
o 02 - credit group for delivery
o 03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items you can have the followings credit limit check:-
u2022 Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022 Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.Max open items %
The customer balance must not exceed a certain percentage.
u2022 Oldest open items
If you donu2019t want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
u2022 Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022 Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.You can use the u201CNextReview dateu201D and u201CNumber of daysu201D fields and combined it with the u201CLast int.reviewu201D field in customer credit master u201CStatusu201D view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
Releasing the Credit Block
These are the three transaction code you can used for releasing the SAP credit management block.
VKM3 - Sales Order
VKM5 - Delivery Order
VKM4 - Both Sales Order and Delivery Order
There are basically two types of customers:
1)Credit worthy
2)Normal customers
Coming to credit worthy customers these customers we can believe and we will give some credit ness for them.For such a type of customers we are going to set them some credit limit.Based on that we will give service to them till that limit.It the limit crosses we will get the messages while creating orders for them.
Their credit limit can be set in FD32 T.Code.
Automatic credit check will be maintained in OVA8
Follow these steps:
1. Go to IMG - enterprise structure - definition - financial accounting - define credit control area.
2. Assignment of company code to credit control area & sales area to credit control area.
3. Go to OVAK select ur sales document type and in the check credit column choose from A B or C. D is for automatic credit control for which you have to maintain the credit group and risk categories.
4. In FD32 you select your customer and click on STATUS icon and press enter. here u maintain the credit amount allowed. but this is done by the Finance people.
5. Now when you create the sales order and if the amount exceeds the credit limit then u will get the message as you maintained in the TC OVAK. Normally the system starts doing credit checks from the second sales.
order.
What are the different types of credit checks?
By Sunilmadho
Credit Check can be :
1) Simple Credit Check
2) Automatic Credit Control
Automatic Credit Control can be at various levels :
1) Order
2) Delivery
3) Goods Issue
Automatic Credit Check is of many types :
1) Static
2) Dynamic
3) MaximumDocument Value
4) Maximum Open Items in percentage
5) Oldest Open Item in number of days
6) Crtitical fields change
7) Highest dunning level, etc.
You can create more.
Credit Check happens only in SD module, never in FI. Because the stage of the check is in the sales cycle, which exists in SD. FI guys will check the credit master sheets of the customer, the MIS, the analysis etc, review the credit limits of customers. But the check will happen only in SD, while creating order, delivery or doing the goods issue.
All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
SM30 - Table/View
u2022     V_TVTW - Define Distribution Channel
u2022     V_TVTA_KKB - Assign sales area to credit control area
u2022     V_T014 - FI - Define Credit Control Area
u2022     T001CM - FI - Assign Permitted Credit Control Area to company code
OVXG - Set up Sales Areas
e.g. Sales Organization
                  Distribution Channel
                              Division
                  Distribution Channel
                              Division
FD32 - Customer Credit Management
OVAK - Define credit limit check by sales document type
u2022     Check Credit
o     A - Credit limit check and warning message
o     B - Credit limit check and error message (no sales order can be created)
o     C - Credit limit check and delivery block (block delivery if hit credit limit)
     Options B and C -> used for checking open order values (when you create/change the sales order)
o     D - Automatic credit control with open order values
     More control in transaction OVA8 - Automatic credit control
     You check for open orders and deliveries, or just open deliveries.
     or open order values with other options
u2022     Credit group
o     Allows you to combine different sales document types for the credit limit check
VKM1 - Blocked SD Documents - Finance have to released the delivery block
OVAD - Define credit limit check by delivery order
u2022     whether the automatic credit check occurs at the time of delivery creation and/or goods issue
OVA7 - Define credit limit check by item category
u2022     Set whether to include/exclude item category for credit limit check
OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
u2022     SAP default credit groups
o     01 - credit group for sales order
o     02 - credit group for delivery
o     03 - credit group for goods issue
OVA8 - Automatic credit control - Double click on the line items
You can have the followings credit limit check :-
u2022     Static
Depends on the customer total value of open orders, deliveries, billing documents and open items.
u2022     Open items
No of days open
Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
Max open items %
The customer balance must not exceed a certain percentage.
u2022     Oldest open items
If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
Days oldest item
No of days allowed for overdue or payment terms.
Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
u2022     Released documents are still unchecked
The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
u2022     Next Review Date
If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
VOKR - Display of work list for credit management (configure the display variant)
In credit mgmt how the Amount & limit can be can be configured at sales order,delivery & PGI Level.
Please give me the solution .
1)First create Credit control area
Path:IMG\ES\Definition\FA\Define Credit Control Area
2) Assign your credit control area to your company code
Path:IMG\ES\Assignment\FA\Assign Company code Credit Control Area
3) And enter the credit limit using above mentioned transaction code FD32.
4) And assign this credit control area in your customer master Sales Org Data (XD02)
5)if you have maintained the credit control area for your customer then goto T.Code FD32.
6)Enter your customer number and the credit control area.
7)Select the status tab.Press enter.
8)Maintain the credit limit in the field.Save.
9)Go to OVA8 T.Code and then click on open orde

Creation of Sales Order using condition records

Dear Experts,
I am creating a sales order using a Function Module : ISM_SALESORDER_CREATEFROMDAT2
In this function module I want to pass the conditon records with which the sales orders needs to be created.
My code is as follows:
LOOP AT it_knumh INTO wa_knumh.
        lwa_bapicondsb-itm_number = wa_knumh-kposn.
        lwa_bapicondsb-cond_type = wa_knumh-kschl.
        lwa_bapicondsb-applicatio = wa_knumh-kappl.
        lwa_bapicondsb-conpricdat = price_date.
        lwa_bapicondsb-cond_no    = wa_knumh-knumh.
        APPEND lwa_bapicondsb TO lit_bapicondsb.
      ENDLOOP.
      CALL FUNCTION 'ISM_SALESORDER_CREATEFROMDAT2'
        EXPORTING
          order_header_in     = lw_bapiheaderb
        IMPORTING
          salesdocument       = lw_docnob
        TABLES
          return              = lit_returnb
          order_items_in      = lit_bapiitemsb
          order_partners      = lit_bapiparnrb
          order_schedules_in = lit_bapischdl
          order_conditions_in = lit_bapicondsb.
I am getting an error as follows:
V4     233     SALES_HEADER_IN has been processed successfully
V4     233     SALES_ITEM_IN has been processed successfully
V4     233     SALES_CONDITIONS_IN has been processed successfully
V1     213     Condition ZMDD is not allowed as header condition
V4     219     Sales document was not changed
where ZMDD - is Discount in Paisa.
please suggest......
Regards,
Abhijit

Dear Abhijeet,
I am afraid that you have put the message in wrong forum.
Kindly put the message in SD / ABAP forum.
Regards,
Rajesh

ALE / IDOC / sales order customer control record change

Similar Messages

Maybe you are looking for