Credit block SAP inbox message

Hello All,
This is my actual requirement:
When the sales order goes into a credit block, KRML output triggers SAP inbox message to the credit manager/credit representative as per the output records maintained.
In standard SAP, the inbox message is read as
"Order for customer XXXX blocked due to credit limit being
exceeded."
where XXXX denotes the customer number.
My requirement is to bring out sales order number, Sales order value, Ship to party name, Reason for Credit block (Like Oldest open item, dynamic check etc) etc in this SAP inbox message.
I checked KRML output mails and titles and i added the above fields as eg. &VBAK-VBELN&, &VBAK-NETWR& etc but this is not getting reflected in the SAP inbox message.
I am unable to figure out from where the standard mail message "Order for customer XXXX blocked due to credit limit being exceeded." is coming from. If the source of this message can be found, other fields can be added to it as per my requirement.
Please let me know if anyone has any idea how to achieve this.

did u checked tcode NACE--->processing routines -->program + form names.
regards
Prabhu

Similar Messages

SAP Inbox messages automatically forwarded to SOST

Hi,
We are in SMR7.0 Sp7.
We have scheduled the deadline monitoring job SWWDHEX and system is generating the message for latest end reached in the useru2019s SAP Inbox as a notification. We understand that the message from SAP Inbox can be forwarded to users email using the automatic forwarding settings through SO12.
However we notice that an email is sent to the user through SOST/SCOT even though we have not maintained the SO12 settings.
Is it standard SAP behavior that a SAP Inbox message is automatically sent to SOST? Or is there any other setting (other than SO12) , that enables the forwarding of SAP Inbox message to SOST? We would like to stop this automatic forwarding of SAP inbox message to SOST.
Thanks
Sukumar

No. Forwarding is standard behavior. It is general behavior, This, you can see in normal R/3 also..
If your problem is NOT resolved as i said, shout BASIS consultants. They will make it worked.
Alert mechanism is different , in SRM 7.0, alert mechanism is given .
Donot get confusion.
Balaji.T.
Edited by: balajit on May 10, 2011 1:55 AM

SAP Inbox message change

Hi,
When people get to their workflow inbox, then message "Waiting for updates" shows. But it is very small and most of the Users don't see it and get out of the Inbox.
Our so many Users reported this problem and want this message to make more clear and big/bold.
Please suggest, how can I do it, I mean where I can make the changes? Is it possible through configuration or java code need to be changed?
Thanks in Advance.
-Vikas

Hi,
Changes wont take effect. this is because UWL is a WebDynPro iview but not a JSP iview, which you can identify based on its look and feel and on the message display format. Any ways, just go through the below document which shows how add a custom coloms to UWL...
/message/7596382#7596382 [original link is broken]
Though this link is not answered you can get some info from here.
below are the docs and link specified...
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70f43b13-284f-2a10-5898-93fe3dc004b4
http://help.sap.com/saphelp_nw04s/helpdata/en/d2/69c045994448adad27d36c4154fe74/frameset.htm
Regards,
SrinivaS

Error While Opening PDF File in SAP Inbox

Hello Experts,
I am facing a weird error in SAP Inbox while opening a PDF files (both created by custom ABAP programs as well as the one attached to a new SAP Inbox message from my desktop & sent to my Inbox as a test).
The error states that "This file does not have a program associated with it for performing this action. Please install program or, if one is already installed, create an association in the Default Programs control panel.".
I checked TCode DC30 also & found an appropriate program is already maintained for PDF.
I couldn't make out more out of this error message. Any inputs in this regard will be highly appreciable.
Regards,
Shaurya

Hi,
Find out the FM that's generating the actual error through de-bug and analyze the same by looking in OSS and or SDN.
Regards
Narasimhan

Classes and methods to send email to SAP inbox

Hi,
I want an appropriate class and method to send emails to SAP Inbox.
My objective is that i convert spool to PDF and send it to SAP inbox as an attachment.
I've used 'CONVERT_ABAPSPOOLJOB_2_PDF' and 'SX_TABLE_LINE_WIDTH_CHANGE' to generate PDF attachment.
I tried Function modules 'SO_DOCUMENT_SEND_API1'/'SO_NEW_DOCUMENT_ATT_SEND_API1' to send email.
It was working fine till now (for last 4 months). Now the Basis team has run some patches due to which the PDFs are getting damaged.
Now the FMs 'SO_DOCUMENT_SEND_API1'/'SO_NEW_DOCUMENT_ATT_SEND_API1' seems to be useless.
So i tried some methods in classes cl_document_bcs and cl_bcs. These are working fine for Internet mails but not SAP mails.
Please suggest me some Classes and methods to send the PDF atachments to SAP inbox.

to have all SAP inbox messages into lotus notes inbox you have to sync the same with the use of connectors rather than resending them
check out this link
http://www-128.ibm.com/developerworks/lotus/library/lei-sap/
for outlook its done using MAPI
http://www.sapgenie.com/faq/exchange.htm
Regards
Raja

SAP Inbox mail message

Dear all,
I am configuring static check with just warning message "Static credit check: credit limit exceeded" for information to credit rep & credit manager & no block at any level as per requirement initially (and delivery block after three months-later activity).this message that the credit limit has been exceeded should go to SAP Inbox of credit representative & a credit manager.
Earlier the message was going to their SAP Inbox while testing but at that time i had configured static check with delivery block & used the routine 9 'credit check block' with source text
'Requirement: Sales order is blocked due to credit'
'If the credit block is set, a mail message should be created'
Now since i am not using routine 9 (because the sales order is not blocked at any level), shall i create a new routine with my abaper to allow me to send a mail message if credit limit has been exceeded or some standard routine is available for the same.
please advise how to proceed.
regards
vikas chhabra

Hello Vikas,
Yes, you need to create your own routine for that.
In Standard there exist only routines 9 and 10 for that purpose.
You can find additional helpful information on that topic in note # 677377, which you find on the SAP Service Marketplace.
Best regards
Martin

Send message to SAP inbox - change message CREATOR

Hi,
I'm sending a message to a user's SAP inbox using function module SO_OBJECT_SEND. By default, the message creator is set to sy-uname. I need to change this to a generic user e.g. 'SYSTEMUSER'. This is not the same as the SENDER/Author/Owner. I managed to change the sender by setting the parameter ORIGINATOR.
I referred to other forums but couldn't find any references to changing the creator. I tried passing the username via parameters SENDER and OWNER - in the Sap Inbox "document overview" the Author is set to SYSTEMUSER but the document creator in "document contents" still reflects my name.
Example code:
ALL FUNCTION 'SO_OBJECT_SEND'
    EXPORTING
      OBJECT_HD_CHANGE = w_object_hd_change
      OBJECT_TYPE      = 'HTM'
      SENDER           = 'SYSTEMUSER'
      OWNER            = 'SYSTEMUSER'
      ORIGINATOR       = 'SYSTEMUSER'
      ORIGINATOR_TYPE = 'B'
    TABLES
      OBJCONT          = text_nom
      RECEIVERS        = receiver_list.
Is it at all possible to change the message creator without modifying the SAP standard code? Examples will be much appreciated.
Kind regards
Liza-Marie

Thanks!!
I'm creating a background job (from within the dialog program) that calls function module SO_OBJECT_SEND with the specified user. This works perfectly!
Regards
Liza-Marie

Credit block should not prevent service order creation

An upgrade from 4.7 to ECC6, without any changes made to the configuration or program change, has lead to the following issue. ECC6 is not creating a service order connected to a sales order, when the customer has exceeded the credit limit. The sales order of custom order type is getting saved with a warning message that credit limit has exceeded. However, earlier in 4.7, the message would not stop creating subsequent service order. What could be different, that prevent ECC6 environment to hold on to service order creation? A subsequent release of the credit block through VKM1 however triggers the service order being created.

Are you using credit card processing in SAP to get the authorization?
If you are then the authorization should not block the order.
Or are you using credit card as a form of payment (without authorization) in which case this needs to be put on the customers account as a payment and then the order entered.
Where are you holding the credit card details?

Cannot save order due to credit block V1849

In VA01, when I try to craete a sales order with Production order/ plan order , I get an information message saying that 'Subsequent function not possible due to credit block.'
It is going into the incomplete logs and requires to provide details for purchase order requistion. That however we cannot complete as credit limit is exceeded.
But as per requirement, the order should be saved even if the credit limit exceeds though the message pops up. the message number is V1849. Can you please tell me how to do that? The purchase order req should be created after release of credit limit.
Switching off credit control for this order type is no solution.
Thanks
Hein

We are also experiencing the same error message in system. The SAP Notes not recommended are not compatable in ECC. In our case the Sale Order is complete but when we try and make any changes it bring an error log which contains this message and when we try and save the documents it brings the below short Dump.
Error analysis
When changing or deleting one or more lines of the internal table
    "\FUNCTION-POOL=V03V\DATA=MVERF_POS-EINTEIL" or when inserting in the table
     "\FUNCTION-POOL=V03V\DATA=MVERF_POS-EINTEIL", 0 was used as
    the line index. An index less than or equal to zero is not
    allowed.
The error can occur when using the following options:
    1. "INDEX idx" for specifying the line number in the table
     "\FUNCTION-POOL=V03V\DATA=MVERF_POS-EINTEIL"
       where you want to change, insert or delete.
    2. "FROM idx" for specifying the start index when deleting a line
       area from or inserting a line area into the table
     "\FUNCTION-POOL=V03V\DATA=MVERF_POS-EINTEIL".
    3. "TO idx" for specifying the end index when deleting a line
       area from or inserting a line area into the table
     "\FUNCTION-POOL=V03V\DATA=MVERF_POS-EINTEIL".
At the time of the termination, the table contained 1 lines.

USER-EXIT - sales order, credit block

Moderator message: moved to correct forum. In future please use meaningful subject.
my requiremnet is, Delivery for an sales order should be created even if it is a credit block i.e even the credit check is unsuccessful the order should be deliverd when we deliver the order from salesdocument->deliver.
i need a user-exit for this to put this check.
can ne one help me.
regards,
pavan,

Hi,
According to Std SAP if in case credit mgmt is activated system will check for credit limit for that customer before delivery.You will be trying to change the std scenario which is not advisable.
However,
Try user exit MV45AFZZ & in that
FORM USEREXIT_SAVE_DOCUMENT_PREPARE.
Also check other exits related to delivery & credit mgmt from
SPRO->Sales & Distr-> System Modifications->User Exits
and check out the documentation part next to each exit in that category.
Regards,
Amit

Credit Managament: avoid credit block for down payment invoices

1) Downpayment - when an order is blocked, can we create a billing
document of the downpayment request created in slaes order. Logically
the customer wants to pay for this downpayment immediately and process
the order
Notes: If credit management is activated at sales order level and In
Milestone Billing scenario or Project Sales order scenario, at Sales
order level we have a Downpayment (Z0000 - Downpayment) Milestone
usage and Other Milestone invoice Usages.
The business requirement is Customer need to pay the downpayment
invoice before executing the Sales order.
In SAP when the Sales order is blocked for Credit Management, system is
not able to create the Downpayment invoice also. to creat the invoice
we have to release the order first. However we dont want to release the
order but want to receivce the downpayment and then may be we can
manually release the order and process. The reason is suppose we have
an automatic release to production or PR or creation of service order,
we would like to process them only after the downapayment, now for
creating the wownpayment invoice for receiving the downpayment, we have
to release the order which shall further process the order
automatically. Please suggest a solution for the same to avoid the
credit block for the Downpayment invoices.

I think this can be enabled easily.
For the combination of Credit Control Area, Credit Group and Risk Category, you should have enabled the Dynamic/Static credit check, you can configure it such a way that it only gives you a warning message and doesnot block your sales order. This should solve ur problem

Sending ALV output to the SAP Inbox.

Hi
I'm using SAP report <b>sendlist_bcs</b> for sending report output to the SAP inbox but attachment is not getting delivered.
Can anybody help to resolve the issue...
My report is:
*& Report ZTTEST_SAGAR
REPORT ZTTEST_SAGAR.
*& Report SENDLIST_BCS
*& Sample report from note 190669 for sending lists via SAPconnect
*& using the BCS interface
*& Note:
*& 1. Set a commit work statement after the sending
*& 2. Give binary data of type x not type c to send module, i.e.
*&     use structure solix instead of soli and give it to tables
*&     parameter contents_hex instead of contents_bin
*&     Do this by filling contents_hex directly from the module
*&     table_compress. In case of reading the data from spool, convert
*&     to solix using so_solitab_to_solixtab
*& 3. Don't calculate document size. It is done internally
*report sendlist_bcs no standard page heading message-id so.
selection-screen begin of block mode with frame title text-001.
parameters: submit radiobutton group mode default 'X'.
parameters: write radiobutton group mode .
parameters: spool radiobutton group mode.
selection-screen end of block mode.
global data
data g_list_content type solix_tab.
data g_text_content type soli_tab.
data sysid(10) TYPE C.
*---- start-of-selection -
start-of-selection.
perform create_text_content changing g_text_content.
perform create_list_content changing g_list_content.
perform send using g_text_content
                     g_list_content.
a commit work has to be set somewhere after the sending!
commit work.
Form routines                                                        *
*&      Form create_list_content
form create_list_content changing list_content type solix_tab.
1st possibility - use "submit <report> exporting list to memory"
if submit = 'X'.
    perform use_submit changing list_content.
endif.
2nd possibility - create a new list within this report.
if write = 'X'.
    perform write_a_list changing list_content.
endif.
3rd possibility - get list from spool
if spool = 'X'.
    perform get_list_from_spool changing list_content.
endif.
endform.                                         "create_list_content
*&      Form create_text_content
form create_text_content changing text_content type soli_tab.
append 'This is the first line' to text_content.         "#EC NOTEXT
append 'This is the second line' to text_content.         "#EC NOTEXT
convert the content from RAW to TXT
call function 'SO_RAW_TO_RTF'
    tables
      objcont_old = text_content
      objcont_new = text_content
    exceptions
      others      = 0.
endform.                                         "create_text_content
*&      Form SEND
form send using text_content type soli_tab
                list_content type solix_tab.
data send_request       type ref to cl_bcs.
data text               type bcsy_text.
data document           type ref to cl_document_bcs.
data recipient          type ref to if_recipient_bcs.
data bcs_exception      type ref to cx_bcs.
data sent_to_all        type os_boolean.
try.
    create the send request
      send_request = cl_bcs=>create_persistent( ).
    create the document with attachments
    main document
      append 'Hi,' to text.
      append 'attached you will find the list.' to text.
      document = cl_document_bcs=>create_document(
                                i_type    = 'RAW'
                                i_text    = text
                                i_subject = 'ABAPlist' ).
    add text attachment to document
      document->add_attachment( i_attachment_type    = 'TXT'
                                i_attachment_subject = text-002
                                i_att_content_text   = text_content ).
    add list attachment to document
      document->add_attachment( i_attachment_type    = 'ALI'
                                i_attachment_subject = text-003
                                i_att_content_hex    = list_content ).
    add document to send request
      send_request->set_document( document ).
      sysid = sy-sysid.
      data : uname type ad_uname.
      uname = 'USTZZSKAZI'.
    create recipient and add to send request
      recipient = cl_cam_address_bcs=>CREATE_RML_ADDRESS( i_syst     = sysid
                                                          i_client   = sy-mandt
                                                          i_username = uname ).
      send_request->add_recipient( i_recipient = recipient ).
    send
      sent_to_all = send_request->send( i_with_error_screen = 'X' ).
      if sent_to_all = 'X'.
       message s022.
      endif.
    catch cx_bcs into bcs_exception.
     message e865 with bcs_exception->error_type.
endtry.
endform.                    "send
*&      Form USE_SUBMIT
form use_submit changing contents_hex type solix_tab.
data listobject type table of abaplist.
get the list object by calling the list in another report
F1 on submit gives more information
submit balvsd03 exporting list to memory and return.
import the list from memory and store it in table listobject
call function 'LIST_FROM_MEMORY'
    tables
      listobject = listobject
    exceptions
      not_found = 1
      others     = 2.
if sy-subrc <> 0.
   message e105 with 'LIST_FROM_MEMORY'.
endif.
free memory
call function 'LIST_FREE_MEMORY'
    tables
      listobject = listobject
    exceptions
      others     = 1.
if sy-subrc <> 0.
   message e105 with 'LIST_FREE_MEMORY'.
endif.
it's always necessary to compress the table.
SAPconnect will decompress it
call function 'TABLE_COMPRESS'                            "#EC *
    tables
      in             = listobject
      out            = contents_hex
    exceptions
      compress_error = 1
      others         = 2.
if sy-subrc <> 0.
   message e105 with 'TABLE_COMPRESS'.
endif.
endform.                               " USE_SUBMIT
*&      Form WRITE_A_LIST
form write_a_list changing contents_hex type solix_tab.
data listobject type table of abaplist.
perform write_list.
Save the list and store table listobject
call function 'SAVE_LIST'
    exporting
      list_index         = sy-lsind
    tables
      listobject         = listobject
    exceptions
      list_index_invalid = 1.
if sy-subrc = 1.
   message e105 with 'SAVE_LIST'.
endif.
It's always necessary to compress the table
SAPconnect will decompress it
call function 'TABLE_COMPRESS'                            "#EC *
    tables
      in             = listobject
      out            = contents_hex
    exceptions
      compress_error = 1
      others         = 2.
if sy-subrc <> 0.
   message e105 with 'TABLE_COMPRESS'.
endif.
endform.                               " WRITE_A_LIST
*&      Form GET_LIST_FROM_SPOOL
form get_list_from_spool changing contents_hex type solix_tab.
data spool_number     type rspoid.
data contents_bin     type soli_tab.
data print_parameters type pri_params.
data valid            type c.
write a list into spool
call function 'GET_PRINT_PARAMETERS'
    importing
      out_parameters         = print_parameters
      valid                  = valid
    exceptions
      archive_info_not_found = 1
      invalid_print_params   = 2
      invalid_archive_params = 3
      others                 = 4.
if sy-subrc <> 0.
   message e105 with 'GET_PRINT_PARAMETERS'.
elseif valid is initial.
    return.
endif.
new-page print on parameters print_parameters no dialog.
perform write_list.
new-page print off.
spool_number = sy-spono.
you can also send OTF documents from spool with this function
module. The importing parameter real_type gives you the doc type
that you have to give to the send interface. The parameter is not
used here
call function 'RSPO_RETURN_SPOOLJOB'
    exporting
      rqident              = spool_number
    tables
      buffer               = contents_bin
    exceptions
      no_such_job          = 1
      job_contains_no_data = 2
      selection_empty      = 3
      no_permission        = 4
      can_not_access       = 5
      read_error           = 6
      type_no_match        = 7
      others               = 8.
if sy-subrc <> 0.
   message e105 with 'RSPO_RETURN_SPOOLJOB'.
endif.
convert to hex table
call function 'SO_SOLITAB_TO_SOLIXTAB'
    exporting
      ip_solitab = contents_bin
    importing
      ep_solixtab = contents_hex.
endform.                               " GET_LIST_FROM_SPOOL
*&      Form WRITE_LIST
form write_list.
data lt_scarr type table of scarr.
data carr type scarr.
select * from scarr into table lt_scarr.
format color = 1.
uline at /1(46).
write: / sy-vline,
         'CARRID',   10 sy-vline,
         'CARRNAME', 35 sy-vline,
         'CURRCODE', 46 sy-vline.
format color = 2.
uline at /1(46).
loop at lt_scarr into carr.
    write: / sy-vline,
           carr-carrid,   10 sy-vline,
           carr-carrname, 35 sy-vline,
           carr-currcode, 46 sy-vline.
endloop.
uline at /1(46).
new-line.
endform.                               " WRITE_LIST
Thanks,
sagar

hi Sagar
'SO_NEW_DOCUMENT_ATT_SEND_API1' function module for that.
Example::::
Data Declaration
data pdf like tline occurs 0.
data : objbin like solisti1   occurs 0 with header line.
Data: docdata    like sodocchgi1,
      objpack    like sopcklsti1 occurs 1 with header line,
      objhead    like solisti1   occurs 1 with header line,
      objtxt     like solisti1   occurs 10 with header line,
       objbin     like solisti1   occurs 10 with header line,
      objhex     like solix      occurs 10 with header line,
      reclist    type table of SOMLRECI1   with header line.
Data: listobject like abaplist   occurs 1 with header line.
data : objhex2 like objhex occurs 0 with header line.
Data: tab_lines type i,
      doc_size   type i,
      att_type   like SOODK-OBJTP.
data: ls_drao like drao occurs 0,
     i_data like drao-orblk occurs 0,
      ls_doc_file like dms_doc_file,
      ls_draw like draw.
data: begin of i_data occurs 0,
      orbkl like drao-orbkl,
       orblk like drao-orblk,
      end of i_data.
data: w_data like i_data,
     w_data2 type drao-orbkl,
      wa_drao type drao.
DATA: t_error(1) type c.
DATA: t_return like BAPIRET2.
*ls_draw-mandt = '200'.
ls_draw-dokar = 'GPO'.
ls_draw-doknr = 'Z10'.
ls_draw-dokvr = '00'.
ls_draw-doktl = '000'.
ls_draw-dttrg = 'SAP-SYSTEM'.
ls_draw-dAPPL = 'DOC'.
ls_doc_file-fileno = '1'.
ls_doc_file-dttrg = 'SAP-SYSTEM'.
*Debug the cv03n transaction to see how the FMs are used
CALL FUNCTION 'CV120_DOC_CHECKOUT_TO_TABLE'
EXPORTING
PS_COUT_DEF       =
    ps_doc_file       =   ls_doc_file
    ps_draw           =   LS_DRAW
tables
PT_DRAZ           =
    ptx_content       =    ls_drao
PTX_DRAOZ         =
EXCEPTIONS
   ERROR             = 1
   OTHERS            = 2
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 at ls_drao into wa_drao.
move: wa_drao-orblk to w_data-orblk.
append w_data to i_data.
endloop.
OBJPACK-HEAD_START = 1.
DESCRIBE TABLE i_data LINES TAB_LINES.
CALL FUNCTION 'ZOUTPUT_X_TABLESIZE_CHG'
EXPORTING
IV_APPEND          = ' '
   IV_BYTE_MODE       = 'X'
IV_STRING          =
IV_XSTRING         =
IMPORTING
EV_SIZE            =
EV_LINES           =
EV_STRING          =
EV_XSTRING         =
TABLES
   IT_DATA            = i_data
   ET_DATA            = objhex
EXCEPTIONS
   NOENTRIES          = 1
   OTHERS             = 2
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 at objhex.
move-corresponding objhex to objhex2.
append objhex2.
endloop.
docdata-obj_name = 'TEST_ALI'.
docdata-obj_descr = 'Test including ALI/HTML Attachment'.
Main Text
objtxt = 'Test Document.'.
append objtxt.
objtxt = 'You will find an ALI/HTML attachment '.
append objtxt.
objtxt = 'Have a nice day.'.
append objtxt.
Write Packing List (Main)
describe table objtxt lines tab_lines.
read     table objtxt index tab_lines.
docdata-doc_size = ( tab_lines - 1 ) * 255 + strlen( objtxt ).
clear objpack-transf_bin.
objpack-head_start = 1.
objpack-head_num   = 0.
objpack-body_start = 1.
objpack-body_num   = tab_lines.
objpack-doc_type   = 'TXT'.
append objpack.
Create Message Attachment
Write Packing List (Attachment)
att_type = 'PDF'.
describe table objhex lines tab_lines.
read     table objhex index tab_lines.
objpack-doc_size = ( tab_lines ) * 255 ."+ strlen( i_data ).
objpack-transf_bin = 'X'.
objpack-head_start = 1.
objpack-head_num   = 0.
objpack-body_start = 1.
objpack-body_num   = tab_lines.
objpack-doc_type   = att_type.
objpack-obj_name   = 'ATTACHMENT1'.
objpack-obj_descr = 'Attached Document1'.
append objpack.
Second attachment
loop at objhex.
move-corresponding objhex to objhex2.
append objhex2.
endloop.
*att_type = 'DOC'.
*describe table objhex lines tab_lines.
*read     table objhex index tab_lines.
*objpack-doc_size = ( tab_lines ) * 255 ."+ strlen( i_data ).
*objpack-transf_bin = 'X'.
*objpack-head_start = 1.
*objpack-head_num   = 0.
*objpack-body_start = 1.
*objpack-body_num   = tab_lines.
*objpack-doc_type   = att_type.
*objpack-obj_name   = 'ATTACHMENT2'.
*objpack-obj_descr = 'Attached Document2'.
*append objpack.
Third attachment
*loop at objhex.
move-corresponding objhex to objhex2.
append objhex2.
*endloop.
*att_type = 'PDF'.
*describe table objhex lines tab_lines.
*read     table objhex index tab_lines.
*objpack-doc_size = ( tab_lines ) * 255 ."+ strlen( i_data ).
*objpack-transf_bin = 'X'.
*objpack-head_start = 1.
*objpack-head_num   = 0.
*objpack-body_start = 1.
*objpack-body_num   = tab_lines.
*objpack-doc_type   = att_type.
*objpack-obj_name   = 'ATTACHMENT3'.
*objpack-obj_descr = 'Attached Document3'.
*append objpack.
Create receiver list
data: reclist1 type sadrfd .
reclist1-rec_fax = '650-467-2890'.
reclist1-REC_STATE = 'US'.
append reclist1.
*read table reclist1 index 1.
move reclist1(30) to reclist-receiver(30).
move reclist1346(3) to reclist-receiver346(3).
*reclist-receiver = reclist1."'US16503457900'.
*move reclist1-rec_fax to reclist-receiver.
*reclist-receiver = 'US16502796630'. "'+1 (16502796999)'.
reclist-REC_type = 'F'.
*reclist-country = 'US'.
*reclist-COM_TYPE = 'TELFAX'.
*reclist-fax = 'US1650-279-6630'.
append reclist.
*reclist-receiver = sy-uname.                "<-- change internal user
*reclist-rec_type = 'B'.
*append reclist.
Send Message
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
    document_data                     = docdata
     PUT_IN_OUTBOX                     = 'X'
     COMMIT_WORK                       = 'X'     "used from rel.6.10
IMPORTING
    SENT_TO_ALL                        =
    NEW_OBJECT_ID                     =
tables
    packing_list                      = objpack
    OBJECT_HEADER                     = objhead
    CONTENTS_BIN                      = objbin
    CONTENTS_TXT                      = objtxt
     CONTENTS_HEX                      = objhex
    OBJECT_PARA                        =
    OBJECT_PARB                        =
    receivers                         = reclist
   EXCEPTIONS
     TOO_MANY_RECEIVERS               = 1
     DOCUMENT_NOT_SENT                = 2
     DOCUMENT_TYPE_NOT_EXIST          = 3
     OPERATION_NO_AUTHORIZATION       = 4
     PARAMETER_ERROR                  = 5
     X_ERROR                           = 6
     ENQUEUE_ERROR                     = 7
     OTHERS                            = 8
IF sy-subrc <> 0.
message ID 'SO' TYPE 'S' NUMBER '023'
          with docdata-obj_name.
ENDIF.
**Please reward suitable points***
With Regards
Navin Khedikar

Output SAP Mail Message - Payer Number and Name

Hi,
I'm trying to set up our sap system to output a message if a sales order goes into credit block. I have all this working and the last part of the request is to include the payer number and name for the sales order on the mail.
I have set up the following against my output
Replacement of Text Symbols
Program: SAPMV45A
Form Routine: TEXT_SYMBOL_REPLACE
and then I have the following mail title:
Sales Order on Credit Block - PAYER:&XVBAK-KNKLI&
I would like to include the name in this, or in the text for the message but I do not know how to extract this. Any ideas?
Many thanks,
Steph.

Christopher,
if you now have set up the WSMessageListener, this one can also be called by external functions. Alternatively you can call any MII transaction as a webservice.
For example, you can use something like this:
http://<server>:<port>/XMII/WSDLGen/<folder>/<tran>
You can also user the runner service (the example gives a pdf output):
http://<server>:<port>/XMII/Runner?Transaction=<folder>/<Transaction-name>
&<InpuParamName1>=<value1>
&<InpuParamName n>=<value n>
&OutputParameter=pdfOutput
&Content-Type=application/pdf
&isBinary=true
&XacuteLoginName=<username>&XacuteLoginPassword=<password>
Michael

Credit-blocked deliveries requires to be excluded from shipments

Hello SAP Champs,
I have following requirement :
I wants to stop credit blocked deliveries being selected in shipment. Is there any user exit available to do the same ?....Is there any other way around to fulfill the same requirement ?...
Thanks & Regards,
Tarpan Vadaliya
SAP SD Consultant

Hi Tarpan,
Sorry, I didn't understand you properly.
I never did it, but in SPRO > LE > Transportation > Shipments > Define Shipment Types (or SM30 for V_TVTK) you have a field for a VOFM subroutine in 'copy routine'. See the help (F1), where it tells you that you can set consistency checks. I think that it doesn't avoid the copy (I'm not sure, as I told you, I never did it) but you can try to manage with error messages. Perhaps if other colleague has do it before, he or she could tell us about it. It's an idea.
I hope this helps you
Regards
Eduardo

VKM1-- Released from Credit Block...But unable to delivery

Hi,
We have credit check activated at sale order level. Due to credit limit, few of sales order blocked for delivery. As of now confirm qty is zero ony.
We have increased credit limit and released sales order from credit block through VKM1 and got successfull messages saying "Sales Order has been released".
But in Sales order, at Header level, its still showing credit block against delivery and unable to make delivery. ( Confirm qty is zero only). Here i am just checking whether block removed or not from VKM1.
Kindly explain and confirm the above process is correct or not.
Guide us the cycle how to release zero confrimed qty SOs.
Regards,
Venkat

Hi Venkat,
It is Right to use VKM1 because where ever i faced this issue a lot while doing PGI in the Outbound Delivery.
just go to VKM1 and give the customer number and Sales Organisation and Distribution channel and Press Execute Button.
The Specific Row of Data which displays your Sales Order Number and Outbound Delivery Number.
Check the Green Color Flag to release the Block on the Sales Order and then try your rest of processing.
Thanks & Regards,
S.Saravanan.
Sap SD - Team.
Edited by: Saravanan Sambandam on May 28, 2008 9:21 AM

Credit block SAP inbox message

Similar Messages

Maybe you are looking for