Error while creating BOM with FM CSAP_MAT_BOM_MAINTAIN

Hi All,
While creating the bom with the FM "CSAP_MAT_BOM_MAINTAIN" using change number i am getting the below error message.
" Processing of this object is not supported with change number."
Please help me out.
Regards
Suresh

call function 'CSAP_MAT_BOM_MAINTAIN'
exporting
    material                 = material
    plant                    = plant
    bom_usage                = usage
    alternative              = alternat
    valid_from               = y_date
*   CHANGE_NO                =                   "<----Have u used this field for creating ?
*   REVISION_LEVEL           =
    i_stko                   = l_stko
*   FL_NO_CHANGE_DOC         = ' '
    fl_commit_and_wait       = 'X'
    fl_bom_create            = 'X'
    fl_new_item              = ' '
    fl_complete              = ' '
* IMPORTING
*   FL_WARNING               =
*   O_STKO                   =
CSAP_MAT_BOM_CREATE would be an ideal one for creation and CSAP_MAT_BOM_MAINTAIN for change
Regards,
Mithun Shetty.

Similar Messages

Error while creating BOM

Hi
iam facing error while creating, changing and display BOM.
Error: Status MHCO of the user interface SAPLCSDI missing.
rgads

Dear,
MHCO - BOM item screen GUI status..Are you using any Alternative item?
Have you applied any new patch in the system?
Contact ABAPer, can give more details
In SAP service place serach for this interface program,,,you will get many notes on this.

Error while creating delivery with reference to STO

Hi,
I am getting the following error while creating the delivery with reference to STO
Document is incomplete: You cannot save the delivery
Diagnosis:
When the system checked whether saving delivery was
permitted, it determined that the requirements stored in
Define Incompletion Procedures for this document do not
allow this subsequent function.
I have checked the following already:
1. Maintained shipping data for both the supplying and receiving plants.
2. Shipping tab exists in the PO
3. Shipping point determination is checked.
4. Customer masters created for both supplying plants and receiving plant for the sales area created for STO
5. Material master is available in both receiving and supplying plants.
It is working fine in one client. and giving a problem only in the other.not able to figure out where the error is. appreciate your suggestions
regards
joe

Hi Joseph,
First go to transaction "VUA4" and see what is the incompletion procedure asigned to your delivery type. Then go to
"OVA2" and see what are the fileds maintained in incompletion procedure of the delivery type and the status groups assigned to them. Now you go to "OVA0(ZERO) and see whether the status group allows to save the delivery. If it doesn't you can untick that check box. But if this is a live system , i doubt if you would be bale to do that. Any way one of the possible causes is storgae location missing. Kindly pelase let me know If you need any more infromation on this.
Regards,
Ram Pedarla

Error while creating BOM using BAPI (urgent)

Hi all,
Thanks for ur help. i am getting some error while creting a BOM using that BAPI
BAPI_MATERIAL_BOM_GROUP_CREATE.
errors are
1) Error/warning when checking the structure of the BOM group with ID =
2)Alternative does not exist for material assignment to material BAPIBOMFG1
is it mandatory to pass the bom group id to this bapi?
In bomgroup structure , i am not passing anything to BOM_GROUP field.
is it mandatory to pass this data? i am giving my coding below.plz suggest , where i am making mistake. it is urgent.
regards
pabitra
report z_bom_create
line-size 132
line-count 65
no standard page heading.
*-- DATA DECLARATION--
include <icon> .
*---Tables
tables : s076, t100, marc .
*---Types
types : begin of t_upload, " Upload file data
col1(18),
col2(10),
col3(30),
col4(12),
col5(50),
end of t_upload,
begin of t_split,
location like stpu-ebort,
end of t_split.
data:begin of i_return occurs 10.
include structure bapiret2.
data:end of i_return.
types:begin of t_item."occurs 10.
include structure BAPI1080_ITM_C.
types:end of t_item.
types:begin of t_subitem." occurs 10.
include structure BAPI1080_SUI_C.
types:end of t_subitem.
types:begin of t_header." occurs 10.
include structure BAPI1080_MBM_C.
types:end of t_header.
types:begin of t_bomgroup." occurs 10.
include structure BAPI1080_BGR_C.
types:end of t_bomgroup.
types:begin of t_variant." occurs 10.
include structure BAPI1080_BOM_C.
types:end of t_variant.
*--- Tables
data: i_upload type standard table of t_upload, " to hold data
i_upload1 type standard table of t_upload,
i_split type standard table of t_split,
i_item type standard table of t_item,
i_subitem type standard table of t_subitem,
i_header type standard table of t_header,
i_bomgroup type standard table of t_bomgroup,
i_variant type standard table of t_variant.
data: wa_upload type t_upload, " to hold file data,
wa_upload1 type t_upload, " to hold plan data,
wa_split type t_split,
wa_item type t_item,
wa_subitem type t_subitem,
wa_header type t_header,
wa_bomgroup type t_bomgroup,
wa_variant type t_variant.
data:v_matnr like mara-matnr,
v_start like sy-index,
v_count(3) type c.
*--Constants
data: c_dot type c value '.',
c_x type c value 'X',
c_comma type c value ','.
-------Selection Screen Design -
*Selection screen for input of upload file address
selection-screen skip 2.
selection-screen begin of block blk1 with frame.
parameters : p_file like rlgrap-filename obligatory .
parameters : p_matnr like mara-matnr obligatory,
p_werks like marc-werks obligatory memory id wrk,
p_stlan like afko-stlan obligatory default '1' .
selection-screen end of block blk1.
---AT SELECTION SCREEN -
at selection-screen on value-request for p_file.
*--For popup to select file.
perform f_give_help.
at selection-screen on p_matnr.
perform f_check_matnr.
-----START OF SELECTION -
*--Data upload using WS_Upload.
perform f_get_data.
perform f_get_bom_data.
perform f_get_bom_data1.
perform f_call_bapi.
*& Form f_give_help
text
--> p1 text
<-- p2 text
FORM f_give_help.
call function 'WS_FILENAME_GET'
exporting
mask = ',.,..'
mode = 'O'
importing
filename = p_file
exceptions
inv_winsys = 1
no_batch = 2
selection_cancel = 3
selection_error = 4
others = 5.
if sy-subrc <> 0 and not sy-msgty is initial.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
ENDFORM. " f_give_help
*& Form f_check_matnr
text
--> p1 text
<-- p2 text
FORM f_check_matnr.
CALL FUNCTION 'BAPI_MAT_BOM_EXISTENCE_CHECK'
EXPORTING
MATERIAL = p_matnr
PLANT = p_werks
BOMUSAGE = '1'
VALID_FROM_DATE =
VALID_TO_DATE =
TABLES
RETURN = i_return.
ENDFORM. " f_check_matnr
*& Form f_get_data
text
--> p1 text
<-- p2 text
FORM f_get_data.
call function 'WS_UPLOAD'
exporting
CODEPAGE = ' '
filename = p_file
filetype = 'DAT'
tables
data_tab = i_upload
exceptions
conversion_error = 1
file_open_error = 2
file_read_error = 3
invalid_type = 4
no_batch = 5
unknown_error = 6
invalid_table_width = 7
gui_refuse_filetransfer = 8
customer_error = 9
others = 10
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
ENDFORM. " f_get_data
*& Form f_get_bom_data
text
--> p1 text
<-- p2 text
FORM f_get_bom_data.
delete i_upload where col1 is initial.
delete i_upload where col1 cs 'ITEM'.
read table i_upload into wa_upload with key col1 = 'FINISHED GOOD:'.
if sy-subrc = 0.
v_matnr = wa_upload-col2.
if v_matnr <> p_matnr.
message e001(zl) with p_matnr.
endif.
else.
message e000(zl).
endif.
ENDFORM. " f_get_bom_data
*& Form f_get_bom_data1
text
--> p1 text
<-- p2 text
FORM f_get_bom_data1.
loop at i_upload into wa_upload where col1 CS 'FINISHED GOOD'.
v_start = sy-tabix + 1.
loop at i_upload into wa_upload1 from v_start .
if wa_upload1-col1 cs 'FINISHED GOOD'.
exit.
else.
perform f_split_upload_data.
endif.
endloop.
endloop.
ENDFORM. " f_get_bom_data1
*& Form f_split_upload_data
text
--> p1 text
<-- p2 text
FORM f_split_upload_data.
if not wa_upload1-col5 is initial.
if wa_upload1-col5 cs c_comma.
split wa_upload1-col5 at c_comma into table i_split.
loop at i_split into wa_split.
v_count = v_count + 1.
endloop.
if wa_upload1-col4 <> v_count.
wa_upload1-col4 = v_count.
endif.
clear wa_upload1-col5.
clear wa_split.
loop at i_split into wa_split.
wa_upload1-col5 = wa_split-location.
append wa_upload1 to i_upload1.
endloop.
else.
append wa_upload1 to i_upload1.
endif.
else.
append wa_upload1 to i_upload1.
endif.
ENDFORM. " f_split_upload_data
*& Form f_call_bapi
text
--> p1 text
<-- p2 text
FORM f_call_bapi.
clear wa_upload1.
wa_header-material = p_matnr.
wa_header-plant = p_werks.
wa_header-bom_usage = p_stlan.
append wa_header to i_header.
wa_bomgroup-bom_usage = p_stlan.
wa_bomgroup-created_in_plant = p_werks.
append wa_bomgroup to i_bomgroup.
wa_variant-alternative_bom = 1.
wa_variant-base_qty = 1.
wa_variant-valid_from_date = sy-datum.
append wa_variant to i_variant.
loop at i_upload1 into wa_upload1.
wa_item-item_no = wa_upload1-col1.
wa_item-item_cat = wa_upload1-col2.
wa_item-component = wa_upload1-col3.
wa_item-comp_qty = wa_upload1-col4.
append wa_item to i_item.
wa_subitem-subitem_qty = '1'.
wa_subitem-installation_point = wa_upload1-col5.
append wa_subitem to i_subitem.
endloop.
CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
EXPORTING
TESTRUN = ' '
ALL_ERROR = ' '
TABLES
BOMGROUP = i_bomgroup
VARIANTS = i_variant
ITEMS = i_item
SUBITEMS = i_subitem
MATERIALRELATIONS = i_header
ITEMASSIGNMENTS =
SUBITEMASSIGNMENTS =
TEXTS =
RETURN = i_return.
if i_return[] is initial.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
*write: /'BOM created:', stpo-stlnr.
else.
*if not i_return[] is initial.
loop at i_return.
IF i_return-TYPE = 'E'.
errmsg-type = i_return-type.
errmsg-line = i_return-message.
append errmsg.
ULINE /1(108).
write:/ icon_led_RED as icon, i_return-MESSAGE.
ULINE /1(108).
ENDIF.
IF i_return-TYPE = 'W'.
errmsg-type = i_return-type.
errmsg-line = i_return-message.
append errmsg.
ULINE /1(108).
write:/ icon_led_YELLOW as icon, i_return-MESSAGE.
ULINE /1(108).
ENDIF.
ENDLOOP.
*write: / i_return-id, i_return-number, i_return-message(80).
*endloop.
*write: /'Error'.
endif.
ENDFORM. " f_call_bapi

Hi shashi,
Thanks for ur help.i tried after passing the group but it is giving same error.
i am getting the error
"Error/warning when checking the structure of the BOM group with ID= test"
i am gettig the above error when i put bomgroup-bom_group_identification = 'TEST'.
whatever i am putting in this field, the same error is comming having different value.
if i put--- bomgroup-bom_group_identification = ' '. then i will get error
"Error/warning when checking the structure of the BOM group with ID=
if i omit that field, then also , i am getting same error.
plz suggest what r the fields i need to pass for BOMGROUP structure for that bapi?
regards
pabitra

Error while creating BOM using BAPI 'BAPI_BOM_UPLOAD_SAVE'

Hi All,
We are getting an error as 'Data is incomplete' while trying to create BoM using the bapi 'BAPI_BOM_UPLOAD_SAVE', if the item contains Item category as 'T'. But for other item category like 'L' or 'N', the bapi is sucessfull.
The values that we pass to fill the item category 'T' are operation, item_cat, bom_itm_no, COMPON_QTY, FIXED_QTY as 'X', UNMEAS as 'ST', ITEM_TEXT1 and ITEM_TEXT2.
Anyone who has faced same problem or has a solution to the problem, kindly provide a solution.
Regards,
Vijay

The error you receive is because of different config for different Item Categories. Find out from the functional team what fields have they kept mandatory for the item category 'T'. You may not be passing one of those fields in the BAPI.
Try creating a BOM manually for item category 'T' and you may figure our which field you are missing.

Error while creating document with attachment.

Hi,
I am getting an error "An error occured while creating the original attribute for PDF"
I tried with out file attachment, it works as you know it is simple....
I tried with various types of attachments like .TXT and .WRD (changed both wsapplication and docfile parameters), however i get the same error. I tried both from presentation and application server (by providing   pf_ftp_dest                = 'SAPFTPA'    pf_http_dest               = 'SAPHTTPA' )
Any idea on how to solve this?
All i need is create a DMS document with a PDF attachment from application server. Are there any other ways to solve this issue?
ws_docdata-documenttype = 'ARE'.
ws_docdata-description = 'BAPI DMS'.
ws_docdata-statusextern = 'CR'.
ws_file-storagecategory = 'DMS_C1_ST'.
ws_file-wsapplication   = 'PDF'.
ws_file-description = 'Job output'.
ws_file-docfile = 'C:\CAD Integ BAPIS_46.pdf'.
append ws_file to it_files.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
     documentdata               = ws_docdata
IMPORTING
     return                     = v_ret
TABLES
     documentfiles              = it_files   .
BREAK-POINT.
IF v_ret-type CA 'EA'.
ROLLBACK WORK.
WRITE : v_Ret-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = '5'.
ENDIF.
Thanks
Pavan

Hi,
I found that it is due to document type = 'ARE'. I changed hte document type to one of hte standard type 'TST'. It works for presentation server, but does not work for application server. Any ideas? Any help is appreciated with points.
ws_docdata-documenttype = 'TST'.
ws_docdata-description = 'BAPI DMS'.
ws_docdata-statusextern = 'CT'.
ws_docdata-documentnumber = 'ZNG-10000000017'.
ws_file-storagecategory = 'DMS_C1_ST'.
ws_file-wsapplication   = 'PDF'.
ws_file-description = 'Job output'.
ws_file-docfile = p_file.
append ws_file to it_files.
CALL FUNCTION 'BAPI_DOCUMENT_CREATE2'
EXPORTING
    documentdata               = ws_docdata
   pf_ftp_dest                = 'SAPFTPA'
   pf_http_dest               = 'SAPHTTPA'
IMPORTING
   documentnumber             = v_docnum
   documentpart               = v_docpart
   documentversion            = v_docver
   return                     = v_ret
TABLES
   documentfiles              = it_files   .
IF v_ret-type CA 'EA'.
ROLLBACK WORK.
WRITE : v_Ret-message.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = '5'.
ENDIF.
Thanks
Pavan

Error while changing BOM with change number

Hi ALL, Please help me with followed error message, I am using ECM. I created ECR and converted to ECO and then released.
Object management record cannot be generated
Message no. 29046
Diagnosis
You want to change the BOM with the entered change number.
One of the following situations triggered this error message:
1. The indicator that allows automatic generation is not set for object type BOM in the change master.
2. The indicator generation only on initial creation is set for object type BOM
3. You are processing a change request.
System response
The system checks whether the indicator object management record will be generated is set in the change master.
If the indicator generation only on initial creation is set, the system checks whether the BOM exists in the system.
Procedure
If you are authorized to change the change master, execute the following steps:
For 1.)
Set this indicator for object type BOM or create the control record in the change master.
For 2.)
If the BOM already exists in the system and the generation only on initial creation indicator is set, the system can no longer generate the control record automatically.
In this case you have to add the object control record to the change master first, then you can change the BOM in relation to the change number.
For 3.)
You cannot generate any object control records for a change request.

Hi
With your question regarding changing BOM with change number it looks lke there may be problem in defining the Object types,objects.Moreover whenever converted to ECO you need to enter into cs02 tcode for changing the bom with relevant change number and valid from date.
Hope this gives you a clear idea.let me know if you need anyfurther inputs.
Regards
Praveen

Error while creating snapshot with OEL6.5 guest in VMware.

While creating snapshots we are getting the following kernel messages:
------------[ cut here ]------------
WARNING: at fs/ext4/super.c:341 ext4_journal_start_sb+0x129/0x140 [ext4]()
Hardware name: VMware Virtual Platform
Modules linked in: autofs4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ppdev vmw_balloon parport_pc parport coretemp hwmon crc32c_intel ghash_clmulni_intel microcode pcspkr sg i2c_piix4 vmw_vmci shpchp ext4 jbd2 mbcache sd_mod crc_t10dif sr_mod cdrom aesni_intel ablk_helper cryptd lrw aes_x86_64 xts gf128mul mptspi mptscsih mptbase scsi_transport_spi vmxnet3 floppy pata_acpi ata_generic ata_piix vmwgfx ttm drm i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: speedstep_lib]
Pid: 4123, comm: master Not tainted 3.8.13-44.1.1.el6uek.x86_64 #2
Call Trace:
[<ffffffff8105d67f>] warn_slowpath_common+0x7f/0xc0
[<ffffffffa019abd7>] ? ext4_dirty_inode+0x27/0x60 [ext4]
[<ffffffff8105d6da>] warn_slowpath_null+0x1a/0x20
[<ffffffffa01b7f89>] ext4_journal_start_sb+0x129/0x140 [ext4]
[<ffffffffa019abd7>] ext4_dirty_inode+0x27/0x60 [ext4]
[<ffffffff811bae4f>] __mark_inode_dirty+0x3f/0x1f0
[<ffffffff811ab026>] update_time+0xa6/0xe0
[<ffffffff811ab0f8>] file_update_time+0x98/0xe0
[<ffffffff8119a90d>] pipe_write+0x34d/0x6b0
[<ffffffff81191b87>] do_aio_write+0xc7/0xd0
[<ffffffff8101a719>] ? emulate_vsyscall+0x329/0x3d0
[<ffffffff81191c37>] do_sync_write+0xa7/0xe0
[<ffffffff81191fc4>] vfs_write+0xb4/0x130
[<ffffffff811a47d5>] ? poll_select_set_timeout+0x95/0xb0
[<ffffffff8119276f>] sys_write+0x5f/0xa0
[<ffffffff815a0a59>] system_call_fastpath+0x16/0x1b
---[ end trace 4525293ca5c40077 ]---
According to Jan Kara:
It seems like you are hitting the warning:
WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);
which means that writing to a named pipe is modifying timestamp of a file while filesystem is frozen. This is not harming the fs such but the fs snapshot you are presumably taking may be slightly inconsistent.
I see the process which is writing to the named pipe is "postfix". Had anyone else seen this behavure before and meaby have a solution for it?

kernel/git/torvalds/linux.git - Linux kernel source treehttp://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7e775f46a125f894a1d71e96797c776dbec161f0has it fixed.
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7e775f46a125f894a1d71e96797c776dbec161f0

Error while creating table with clusters

Hi
I tried the following
CREATE CLUSTER emp_dept (deptno NUMBER(3))Cluster is created
Then i tried to create the table having the above cluster but giving the errors:
create table emp10 (ename char(5),deptno number(2) )cluster emp_dept(deptno);The error is:
ORA-01753 column definition incompatible with clustered column definitionCould you please help me in this

Your cluster is based on a NUMBER(3) data type while the emp10 table has a deptno column with a data type of NUMBER(2).

Error while creating MBO with web service data source

Hi All,
I am trying to create MBO by selecting web service as a data source type in SMP 2.3. I am providing sharepoint webservice url of type wsdl with HTTP basic authentication. However, I am getting following error can anyone help me in that. Looking for detail explaination as this is new for me...
(For "define XSLT manually" I am using sample .xsl file)
Regards,
Harshada

Harshada Karane
Are you using any proxy in your browser? If yes, please set the proxy in workspace and then trHow to bypass proxy settings in SMP workspace for connecting any public Web Service within corporate Network
Rgrds
JK

Error while creating PR with account assignment K

Hello All,
We have a issue for one user , he is trying to created PR in ME51N in production system but cannot and he gets the error message " Field selection PT8B not defined'. Infact the the field selection PT8B itself is not there in the configuration. But in quality system the user is able to create PR without any issue.
Also his colleague can able to create the PR in production in ME51N without any issues. Even i am able to create the PR in ME51N in quality system without any problem , i came across the exact issue in the below thread , since the issue is only for that specific user , i am not able to find the cause.
EROR while saving PR
Pls provide your inputs/suggestions
Thanks
Benny

Hi Benny,
There's possibility to assign different screen layouts to different users 8and of course the screen layout for the same users in different systems can be different). It is included in "functional auth. for byers" and can be found in IMG under Purchasing -> Auth. mgmt. Each code here has among other fields a field called "field selection", which presumably contains PT8B for one of the func. auth. codes. This func. auth. code is in turn linked to the user master record by means of the parameter EFB ("own data" or trs SU3 or trs SU01).
Therefore it is very much possible that the different users are allocated to the different func. auth. codes and the same user in the quality system is allocated to the different func. auth. code than in prod.
BR
Raf

Error while creating function with record type as return type

Hi i tried the following code to get the nth highest sal using record type and function.
CREATE OR REPLACE PACKAGE pack_rec_cur AS
TYPE rec_type IS RECORD (
name EMP.ename%TYPE,
sal EMP.sal%TYPE);
END;The above package is created
CREATE OR REPLACE
FUNCTION fun_rec_cur(n INT) RETURN pack_rec_cur.rec_type AS
   rec pack_rec_cur.rec_type;
    CURSOR cur_rec IS
      SELECT ename,sal
        FROM emp
         WHERE sal is not null
          ORDER BY DESC;
BEGIN
OPEN cur_rec;
FOR i IN 1..n LOOP
   FETCH cur_rec into rec;
   EXIT WHEN cur_rec%NOTFOUND;
END LOOP;
CLOSE cur_rec;
RETURN rec;
END;   The above function is giving errors
LINE/COL ERROR
4/7      PL/SQL: SQL Statement ignored
7/16     PL/SQL: ORA-00936: missing expression
SQL> Could you please correct me where i'm doing mistake
Thanks.

You are missing the column name in order by clauase. Is it ename desc?
CREATE OR REPLACE
FUNCTION fun_rec_cur(n INT) RETURN pack_rec_cur.rec_type AS
   rec pack_rec_cur.rec_type;
    CURSOR cur_rec IS
      SELECT ename,sal
        FROM emp
         WHERE sal is not null
          ORDER BY ENAME DESC; ---added ename
BEGIN
OPEN cur_rec;
FOR i IN 1..n LOOP
   FETCH cur_rec into rec;
   EXIT WHEN cur_rec%NOTFOUND;
END LOOP;
CLOSE cur_rec;
RETURN rec;
END;
-OUTPUT
SQL> SET SERVEROUT ON
SQL>
SQL> DECLARE
2     rec            pack_rec_cur.rec_type;
3 BEGIN
4     rec         := fun_rec_cur (6); --you get the 6th record in order of ename desc
5     DBMS_OUTPUT.put_line ('ename::' || rec.NAME || ' sal ::' || rec.sal);
6 END;
7 /
ename::MARTIN sal ::1250
PL/SQL procedure successfully completed.
SQL>

Error while creating RMA with Original Order

Hi All,
Can any one pls help to troubleshoot this error. I'm using oe_order_pub.process_order API.
Error:
message is :ORA-06502: PL/SQL: : NULL value of a key of the index table an error of number or value in a package OE_Order_PVT, procedure Lines
message index is :1
Debug = F
Debug
Level = 5
Part of code:
IF (l_debug_level > 0)
THEN
l_debug_file := oe_debug_pub.set_debug_mode('FILE');
oe_debug_pub.initialize;
oe_debug_pub.setdebuglevel(l_debug_level);
oe_msg_pub.initialize;
END IF;
l_line_tbl.delete;
/*****************POPULATE REQUIRED ATTRIBUTES **********************************/
FOR v_cur_header IN cur_header(l_header_id)
LOOP
/*****************INITIALIZE HEADER RECORD******************************/
l_header_rec := oe_order_pub.g_miss_header_rec;
l_header_rec.operation := oe_globals.g_opr_create;
l_header_rec.order_type_id := l_transaction_type_id;
l_header_rec.sold_to_org_id := v_cur_header.sold_to_org_id;
l_header_rec.ship_from_org_id := v_cur_header.ship_from_org_id;
l_header_rec.price_list_id := v_cur_header.price_list_id;
l_header_rec.pricing_date := SYSDATE;
l_header_rec.orig_sys_document_ref := v_cur_header.orig_sys_document_ref;
l_header_rec.transactional_curr_code := v_cur_header.transactional_curr_code;
l_header_rec.flow_status_code := v_cur_header.flow_status_code;
/*****************INITIALIZE ACTION REQUEST RECORD*************************************/
l_action_request_tbl(1) := oe_order_pub.g_miss_request_rec;
/*****************INITIALIZE LINE RECORD********************************/
FOR v_cur_lines IN cur_lines(v_cur_header.header_id)
LOOP
l_line_tbl(l_line_tbl.COUNT) := oe_order_pub.g_miss_line_rec;
l_line_tbl(l_line_tbl.COUNT).operation := oe_globals.g_opr_create;
l_line_tbl(l_line_tbl.COUNT).return_reason_code := 'CANCELLATION'; -- Mandatory for RMA
l_line_tbl(l_line_tbl.COUNT).reference_line_id := v_cur_lines.line_id; -- Original order line_id
l_line_tbl(l_line_tbl.COUNT).reference_header_id := v_cur_header.header_id; -- Original order header_id
l_line_tbl(l_line_tbl.COUNT).return_context := 'ORDER';
l_line_tbl(l_line_tbl.COUNT).return_attribute1 := v_cur_header.header_id; -- Original order header_id
l_line_tbl(l_line_tbl.COUNT).return_attribute2 := v_cur_lines.line_id; -- Original order line_id
l_line_tbl(l_line_tbl.COUNT).inventory_item_id := v_cur_lines.inventory_item_id;
l_line_tbl(l_line_tbl.COUNT).ordered_quantity := v_cur_lines.ordered_quantity;
END LOOP;
END LOOP;
/*****************CALLTO PROCESS ORDER API*********************************/
OE_Order_PUB.Process_Order(
p_api_version_number => l_api_version_number,
p_header_rec => l_header_rec,
p_line_tbl => l_line_tbl,
p_action_request_tbl => l_action_request_tbl,
-- OUT variables
x_header_rec => l_header_rec_out,
x_header_val_rec => l_header_val_rec_out,
x_header_adj_tbl => l_header_adj_tbl_out,
x_header_adj_val_tbl => l_header_adj_val_tbl_out,
x_header_price_att_tbl => l_header_price_att_tbl_out,
x_header_adj_att_tbl => l_header_adj_att_tbl_out,
x_header_adj_assoc_tbl => l_header_adj_assoc_tbl_out,
x_header_scredit_tbl => l_header_scredit_tbl_out,
x_header_scredit_val_tbl => l_header_scredit_val_tbl_out,
x_line_tbl => l_line_tbl_out,
x_line_val_tbl => l_line_val_tbl_out,
x_line_adj_tbl => l_line_adj_tbl_out,
x_line_adj_val_tbl => l_line_adj_val_tbl_out,
x_line_price_att_tbl => l_line_price_att_tbl_out,
x_line_adj_att_tbl => l_line_adj_att_tbl_out,
x_line_adj_assoc_tbl => l_line_adj_assoc_tbl_out,
x_line_scredit_tbl => l_line_scredit_tbl_out,
x_line_scredit_val_tbl => l_line_scredit_val_tbl_out,
x_lot_serial_tbl => l_lot_serial_tbl_out,
x_lot_serial_val_tbl => l_lot_serial_val_tbl_out,
x_action_request_tbl => l_action_request_tbl_out,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data
/*****************CHECK RETURN STATUS***********************************/
IF l_return_status = fnd_api.g_ret_sts_success
THEN
IF (l_debug_level > 0)
THEN
dbms_output.put_line('success');
END IF;
COMMIT;
/* OE_ORDER_BOOK_UTIL.COMPLETE_BOOK_ELIGIBLE(1.0,
FND_API.G_FALSE,
l_header_rec_out.header_id,
b_return_status,
b_msg_count,
b_msg_data
COMMIT;
ELSE
IF (l_debug_level > 0)
THEN
dbms_output.put_line('failure');
END IF;
ROLLBACK;
END IF;
/*****************DISPLAY RETURN STATUS FLAGS******************************/
IF (l_debug_level > 0)
THEN
dbms_output.put_line('process ORDER ret status IS: ' ||
l_return_status);
dbms_output.put_line('process ORDER msg data IS: ' || l_msg_data);
dbms_output.put_line('process ORDER msg COUNT IS: ' || l_msg_count);
dbms_output.put_line('header.order_number IS: ' ||
to_char(l_header_rec_out.order_number));
dbms_output.put_line('header.return_status IS: ' ||
l_header_rec_out.return_status);
dbms_output.put_line('header.booked_flag IS: ' ||
l_header_rec_out.booked_flag);
dbms_output.put_line('header.header_id IS: ' ||
l_header_rec_out.header_id);
dbms_output.put_line('header.order_source_id IS: ' ||
l_header_rec_out.order_source_id);
dbms_output.put_line('header.flow_status_code IS: ' ||
l_header_rec_out.flow_status_code);
END IF;
IF (l_debug_level > 0)
THEN
FOR i IN 1 .. l_msg_count
LOOP
oe_msg_pub.get(p_msg_index => i,
p_encoded => fnd_api.g_false,
p_data => l_data,
p_msg_index_out => l_msg_index);
dbms_output.put_line('message is :' || l_data);
dbms_output.put_line('message index is :' || l_msg_index);
END LOOP;
END IF;
IF (l_debug_level > 0)
THEN
dbms_output.put_line('Debug = ' || oe_debug_pub.g_debug);
dbms_output.put_line('Debug Level = ' ||
to_char(oe_debug_pub.g_debug_level));
dbms_output.put_line('Debug File = ' || oe_debug_pub.g_dir || '/' ||
oe_debug_pub.g_file);
dbms_output.put_line('****************************************************');
oe_debug_pub.debug_off;
END IF;

Thx for your answer!
Yes, I'm using this procedure
PROCEDURE initialize_apps IS
l_user NUMBER;
l_resp NUMBER;
l_appl NUMBER;
BEGIN
SELECT fnd.user_id,
fresp.responsibility_id,
fresp.application_id
INTO l_user,
l_resp,
l_appl
FROM fnd_user fnd,
fnd_responsibility_tl fresp
WHERE fnd.user_name = 'SYSADMIN'
AND upper(fresp.responsibility_name) = 'ORDER MANAGEMENT SUPER USER';
dbms_output.put_line('l_user: ' || l_user);
dbms_output.put_line('l_resp: ' || l_resp);
dbms_output.put_line('l_appl: ' || l_appl);
fnd_global.apps_initialize(l_user,
l_resp,
l_appl);
END;
But, I found problem.
It was my carelessness :) l_line_tbl(l_line_tbl.COUNT) returns 0.

Error while creating the HTTP client with destination GB_DPSRetrieve

Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
Kishore

Hi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar

Error while creating the sales order with billing reference

hi alll
i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
cheers
shalsa007........

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

Error while creating BOM with FM CSAP_MAT_BOM_MAINTAIN

Similar Messages

Maybe you are looking for