Worflow container elements not populating

Hi,
I am using a simple method and populating certain parameters of the method. in stand alone from swo1 the method populates the container element. This method is then called from a task in workflow.
The problem I face is that the workflow container elements are not populated, although the container elements at the task level are populated corectly in the workflow log. Even If I am binding a hardcoded value at the task to workflow binding level, the workflow container elements is not getting correct values; when I check the log and hence the workflow goes in error.
I would like to know why the workflow container elements not getting filled with right values. I have done many workflows before but never faced such an issue before.
Regards,
Vishal Bhatia
Edited by: Vishal Bhatia on Sep 19, 2011 2:33 PM

Hi,
I have checked the binding and workflow is activated again.
Also buffering was done in SWU_OBUF.
I also tried to run the workflow from SWDD itself and still the same problem. This is very strange. Never before i encountered such an error.
Kindly suggest. I also tried to create a new task and change the names of container variables in workflow. The strangest thing is the hardcoding of value also not being passed.
Types of parameters match and import export set accordingly.
Regards,
Vishal Bhatia

Similar Messages

  • Standard Container element not populating....

    Hi All,
    I am using a standard task TS17900100 to process the HCM Form in workflow at 2 places. There is a standard container element STEP_OBJECT of this task which gets populated at run time.
    Now at first place this container is getting populated correctly. But in the second place I have used the same binding and same task but STEP_OBJECT container is not getting populated. Also, STEP_OBJECT is not an import/export parameter.
    Please suggest.
    The task is using  the following class and method :
    CL_HRASR00_WF_COMPONENTS
    WI_EXECUTION_VIA_R3_INBOX

    Hi,
    I have checked the bindings in both the steps. It is same and all the containers are getting populated in the log except STEP_OBJECT. That's why I am not getting the reason for such a case. STEP_OBJECT is getting populated by itself in the first step. But it is not getting populated in the second step.
    Please suggest.
    Regards,
    Guddan

  • Return order BUS2102 Workflow container data not populated

    Hi All,
    Please requesting you to provide your advise on the below issue.
    I have created a custom workflow with business object BUS2102
    In the Workflowtemplate (E.g. WS90000XXX)
    i have included the triggering event for BUS2102 with EVENT "CREATED" and
    added a container element SDReturnCN of type BUS2102
    Once the Return Order is created the Workflow is getting triggered successfully
    but data is not populated into the container SDReturnCN.
    Do i need to write and EXIT to populate container UNLIKE as in Credit memo bussiness object :BUS2094
    if yes please let me know which part i am missing.
    Thanks & Regards,
    Veeru.

    Hello,
    "but data is not populated into the container SDReturnCN."
    Check the bindings. Where is the value coming from?
    regards
    Rick Bakker
    hanabi technology

  • 0PM_ORDER - WBS element not populated by extractor

    Hi all
    Just wondering if anyone has experienced a similar problem.
    We use this data source as part of our PM master data loads. It runs every night, no problem. Iu2019m busy with a new user requirement regarding Project (WBS) costs as posted on PM orders, and I was pleased to see that 0PM_ORDER has field PROID (WBS) on it already u2013 thought I was half way to building my query!
    Except, the field is not populated. Even when I run the extractor on the R/3 system to test (for an order type PM05 on which WBS element is a required entry), I never get any values in this field. I had a look on SDN and OSS and have seen a number of posts about the conversion exits relating to WBS elements, but this presupposes that a value is being populated in the extractor, which in my case is not happening.
    Does anyone have any suggestions?
    Regards, Lara

    0PM_Order extracts the data of WBS element on the tab "location" on the PM order (IW33). It doesnt extract the WBS element on the tab "Additional data".
    I am not sure how these WBS elements are different, your PS consultant might have an answer. Either you can have user exit to fill this field or ask your ECC abap consultant to fill the same in both fields of order, if doesnt make any difference. I am also in same situation, keep me posted if you have have get any new information from your PS consultant or SAP.

  • BPM Alert Container Elements Not Filled

    Hi All,
    Another problem i am facing when i am raising alert from BPM.
    In inbox i see alert message being raised but with no text.
    I have also subscribed to email alerts.
    In the email the subject is Process 000000008058
    and the content is the first alphabet of the AlertMessage container element.
    Ex : In BPM my container element is AlertMessage and the message assigned is <i>Error</i> . Then in email message i only get E. where as in alert inbox i get nothing.
    ps : im using XI 7.0 SP 9. there are no notes which are applicable for this release.
    Regards,
    Rahul
    Message was edited by:
            Rahul Jain

    Hi Bhavesh,
    <i>>When you select Dynamic text in the Alert category, the Container tab will no longer be available in ALRTCATDEF for your Alet Category.!</i>
    the container tab is available but the Long& Short text tab is disabled.
    I did not mean that..
    What i meant was see next to the Properties tab in Alert Category defination there is a Container tab where we define our own container elements.
    Do i need to define the names there..or i can directly use in the BPM?
    Regards,
    Rahul
    Message was edited by:
            Rahul Jain

  • Step Container Element not getting updated

    Hi,
          I have created a step container element for handling comments with the same ABAP dictinary structure & import export       parameter of a existing workflow conatiner element  & binded with the WF container & step conatiner & i have the saved & activated the WF template sucessfully.but when action is being taken from portal on a Workitem then comments are being  passed to the WF container but the step container that i created is not getting updated . i checked in SWI6 , it's showing not set.
    can any help me on this regard.?
    Thanks & Regards
    Rohan Kumar Das

    Actually, I believe the problem is related to binding.
    When called in the foreground, object references (and data references) are present in memory for all subsequent processing.
    You probably need to make the CONTAINER "Persistent".
    In your code, call the macro SWC_CONTAINER_TO_PERSISTENT <container name here>.   For example:
    SWC_CONTAINER local_container.
    SWC_CREATE_CONTAINER local_container.
    "  Set you Container elements
    " SWC_SET_ELEMENT local_container 'Element01' lv_element01.
    " SWC_SET_TABLE local_container 'Element02' lt_table02.
    SWC_CONTAINER_TO_PERSISTENT local_container.
    " Start your workflow passing local_container.
    Something like this...
    Hope this is relevent . . . Apologies if not . . .
    Regards,
    Tom Carruth

  • Over Time Workflow Container elements not updated

    Hi,
    I am using Standard Task TS20000459 for approval of Overtime entered for an employee in CAT2 transaction.
    Work item is getting generated to his manager's inbox.
    Issue is, subject of the work item should have employee number and Employe name. Standard Task contains Container elements &TS_PERNR& and &TS_ENAME& which is not getting filled with any values.
    Can any one suggest me how to get the same?
    Regards,
    Saravana Perumal

    Hi Shanti
    I faced the same problem...And i resolved that problem by binding...
    Create the container element for PERNR and ENAME in the standard task ts20000459 as well as in workflow container.Then bind those container values.
    Before bind the workflow and task container, you have to bind the workflow container with the event container.
    Regards,
    Hemalatha.

  • Container element not available when task is background

    Hi All,
    We have a task and method. the method works fine when tested individually, returns the correct values.
    However when the task is executed in background mode, the element in container is not updated. If the processing mode is foreground, the element is rightly updated in container.
    Clearly it has nothing to do with binding since I get the elements when I execute the task in foreground.
    any ideas would be welcome.
    thanks,
    Gautam

    Actually, I believe the problem is related to binding.
    When called in the foreground, object references (and data references) are present in memory for all subsequent processing.
    You probably need to make the CONTAINER "Persistent".
    In your code, call the macro SWC_CONTAINER_TO_PERSISTENT <container name here>.   For example:
    SWC_CONTAINER local_container.
    SWC_CREATE_CONTAINER local_container.
    "  Set you Container elements
    " SWC_SET_ELEMENT local_container 'Element01' lv_element01.
    " SWC_SET_TABLE local_container 'Element02' lt_table02.
    SWC_CONTAINER_TO_PERSISTENT local_container.
    " Start your workflow passing local_container.
    Something like this...
    Hope this is relevent . . . Apologies if not . . .
    Regards,
    Tom Carruth

  • WBS element not populating at item level

    Hi Gurus,
    <br>I am trying to create a new sales order using the function module SD_SALESDOCUMENT_CREATE but when i pass a <br>value for the WBS element at item level it is not getting populated in the back end system.
    <br>
    <br>  data :LT_RETURN                     TYPE TABLE OF  BAPIRET2,
    <br>         LT_SALES_ITEMS_IN             TYPE STANDARD TABLE OF  BAPISDITM,
    <br>         LT_SALES_ITEMS_INX            TYPE TABLE OF  BAPISDITMX ,
    <br>        LT_SALES_PARTNERS             TYPE TABLE OF  BAPIPARNR ,
    <br>        LT_SALES_SCHEDULES_IN         TYPE TABLE OF  BAPISCHDL ,
    <br>        LT_SALES_SCHEDULES_INX        TYPE TABLE OF  BAPISCHDLX ,
    <br>        LT_SALES_CONDITIONS_IN        TYPE TABLE OF  BAPICOND ,
    <br>        LT_SALES_CONDITIONS_INX       TYPE TABLE OF  BAPICONDX,
    <br>        LT_SALES_CFGS_REF             TYPE TABLE OF  BAPICUCFG ,
    <br>        LT_SALES_CFGS_INST            TYPE TABLE OF  BAPICUINS ,
    <br>        LT_SALES_CFGS_PART_OF         TYPE TABLE OF  BAPICUPRT,
    <br>        LT_SALES_CFGS_VALUE           TYPE TABLE OF  BAPICUVAL ,
    <br>        LT_SALES_CFGS_BLOB            TYPE TABLE OF  BAPICUBLB ,
    <br>        LT_SALES_CFGS_VK              TYPE TABLE OF  BAPICUVK ,
    <br>        LT_SALES_CFGS_REFINST         TYPE TABLE OF  BAPICUREF ,
    <br>        LT_SALES_CCARD                TYPE TABLE OF  BAPICCARD ,
    <br>        LT_SALES_TEXT                 TYPE TABLE OF  BAPISDTEXT ,
    <br>        LT_SALES_KEYS                 TYPE TABLE OF  BAPISDKEY ,
    <br>        LT_SALES_CONTRACT_IN          TYPE TABLE OF  BAPICTR ,
    <br>        LT_SALES_CONTRACT_INX         TYPE TABLE OF  BAPICTRX,
    <br>        LT_EXTENSIONIN                TYPE TABLE OF  BAPIPAREX ,
    <br>        LT_PARTNERADDRESSES           TYPE TABLE OF  BAPIADDR1 ,
    <br>        LT_SALES_SCHED_CONF_IN        TYPE TABLE OF  BAPISCHDL2 ,
    <br>        LT_ITEMS_EX                   TYPE TABLE OF  BAPISDIT ,
    <br>        LT_SCHEDULE_EX                TYPE TABLE OF  BAPISDHEDU ,
    <br>        LT_BUSINESS_EX                TYPE TABLE OF  BAPISDBUSI ,
    <br>        LT_INCOMPLETE_LOG             TYPE TABLE OF  BAPIINCOMP ,
    <br>        LT_EXTENSIONEX                TYPE TABLE OF  BAPIPAREX ,
    <br>        LT_CONDITIONS_EX              TYPE TABLE OF  BAPICOND ,
    <br>        LT_PARTNERS_EX                TYPE TABLE OF  BAPISDPART ,
    <br>        LT_TEXTHEADERS_EX             TYPE TABLE OF  BAPISDTEHD ,
    <br>       LT_TEXTLINES_EX               TYPE TABLE OF  BAPITEXTLI ,
    <br>       LT_BATCH_CHARC                TYPE TABLE OF  BAPIBTSEL ,
    <br>        LT_CAMPAIGN_ASGN              TYPE TABLE OF  BAPISDCA ,
    <br>        LT_CONDITIONS_KONV_EX         TYPE TABLE OF  KONV .
    <br>
    <br>  DATA: LV_SALESDOCUMENT_EX           TYPE           BAPIVBELN-VBELN,
    <br>        LT_SALES_HEADER_OUT           TYPE           BAPISDHD,
    <br>        LT_SALES_HEADER_STATUS        TYPE           BAPISDHDST.
    <br>
    <br>  DATA: LV_VALUE_SALESDOCUMENT        TYPE           BAPIVBELN-VBELN,
    <br>        LT_SALES_HEADER_IN            TYPE           BAPISDHD1,
    <br>        LT_SALES_HEADER_INX           TYPE TABLE OF  BAPISDHD1X,
    <br>        LT_SENDER                     TYPE TABLE OF  BDI_LOGSYS,
    <br>        LV_BINARY_RELATIONSHIPTYPE    TYPE           BRELTYP-RELTYPE,
    <br>        LV_INT_NUMBER_ASSIGNMENT      TYPE           BAPIFLAG-BAPIFLAG VALUE 'R',
    <br>        LV_BEHAVE_WHEN_ERROR          TYPE           BAPIFLAG-BAPIFLAG VALUE ' ',
    <br>        LT_LOGIC_SWITCH               TYPE TABLE OF  BAPISDLS,
    <br>        LV_BUSINESS_OBJECT            TYPE           BAPIUSW01-OBJTYPE VALUE ' ',
    <br>        LT_TESTRUN                    TYPE TABLE OF  BAPIFLAG-BAPIFLAG ,
    <br>        LV_CONVERT_PARVW_AUART        TYPE           BAPIFLAG-BAPIFLAG VALUE ' ',
    <br>        LV_STATUS_BUFFER_REFRESH      TYPE           BAPIFLAG-BAPIFLAG VALUE 'X',
    <br>        LV_CALL_ACTIVE                TYPE           CHAR4.
    <br>
    <br>  DATA: WA_SALES_PARTNERS             LIKE LINE OF   LT_SALES_PARTNERS,
    <br>        WA_SALES_SCHEDULES_IN         LIKE LINE OF   LT_SALES_SCHEDULES_IN,
    <br>        WA_SALES_CONDITIONS_IN        LIKE LINE OF   LT_SALES_CONDITIONS_IN,
    <br>        WA_EXTENSIONIN                LIKE LINE OF   LT_EXTENSIONIN,
    <br>        WA_SALES_ITEMS_IN             LIKE LINE OF   LT_SALES_ITEMS_IN,
    <br>        WA_SALES_TEXT                 LIKE LINE OF   LT_SALES_TEXT.
    <br>
    <br>  LT_SALES_HEADER_IN-DOC_TYPE       = 'ZSAL'.
    <br>  LT_SALES_HEADER_IN-SALES_ORG      = '1000'.
    <br>  LT_SALES_HEADER_IN-DISTR_CHAN     = '02'.
    <br>  LT_SALES_HEADER_IN-DIVISION       = '01'.
    <br>  LT_SALES_HEADER_IN-PMNTTRMS       = 'Z020'.
    <br>  LT_SALES_HEADER_IN-DUN_COUNT      = '0'.
    <br>  LT_SALES_HEADER_IN-ADD_VAL_DY     = '00'.
    <br>  LT_SALES_HEADER_IN-EXCHG_RATE     = '0'.
    <br>   LT_SALES_HEADER_IN-BILL_DATE      = SY-DATUM.
    <br>
    <br>data lv_kunnr type kunnr value '106475'.
    <br>
    <br>CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    <br>  EXPORTING
    <br>    INPUT         = lv_kunnr
    <br> IMPORTING
    <br>   OUTPUT        = lv_kunnr.
    <br>
    <br>  WA_SALES_PARTNERS-PARTN_ROLE      = 'AG'.
    <br>  WA_SALES_PARTNERS-PARTN_NUMB      = lv_kunnr.
    <br>  APPEND WA_SALES_PARTNERS TO LT_SALES_PARTNERS.
    <br>
    <br>  WA_SALES_PARTNERS-PARTN_ROLE      = 'WE'.
    <br>  WA_SALES_PARTNERS-PARTN_NUMB      = lv_kunnr.
    <br>  APPEND WA_SALES_PARTNERS TO LT_SALES_PARTNERS.
    <br>
    <br>  WA_SALES_TEXT-ITM_NUMBER = '000010'.
    <br>  WA_SALES_TEXT-TEXT_ID = 'ZS01'.
    <br>  WA_SALES_TEXT-LANGU =  SY-LANGU.
    <br>  APPEND WA_SALES_TEXT TO LT_SALES_TEXT.
    <br>
    <br>  WA_SALES_TEXT-ITM_NUMBER = '000010'.
    <br>  WA_SALES_TEXT-TEXT_ID = '3010'.
    <br>  WA_SALES_TEXT-LANGU =  SY-LANGU.
    <br>  APPEND WA_SALES_TEXT TO LT_SALES_TEXT.
    <br>
    <br>  WA_SALES_SCHEDULES_IN-ITM_NUMBER  = '000010'.
    <br>  WA_SALES_SCHEDULES_IN-REQ_QTY     = '22'.
    <br>  APPEND WA_SALES_SCHEDULES_IN TO LT_SALES_SCHEDULES_IN.
    <br>
    <br>  WA_SALES_CONDITIONS_IN-ITM_NUMBER = '000010'.
    <br>  WA_SALES_CONDITIONS_IN-COND_TYPE  = 'ZMAN'.
    <br>  WA_SALES_CONDITIONS_IN-CURRENCY   = 'NOK' .
    <br>  APPEND WA_SALES_CONDITIONS_IN TO LT_SALES_CONDITIONS_IN.
    <br>
    <br>  WA_EXTENSIONIN-STRUCTURE          = 'BAPE_VBAK'.
    <br> *  WA_EXTENSIONIN-VALUEPART1         = '090000000200'.
    <br>  APPEND WA_EXTENSIONIN TO LT_EXTENSIONIN.
    <br>
    <br>data lv_MATNR type MATNR value '000000000000000031'.
    <br>
    <br>CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    <br>  EXPORTING
    <br>    INPUT         = lv_MATNR
    <br> IMPORTING
    <br>   OUTPUT        = lv_MATNR.
    <br>
    <br>  WA_SALES_ITEMS_IN-ITM_NUMBER      = '10'.
    <br>  WA_SALES_ITEMS_IN-MATERIAL        = lv_MATNR.
    <br>  WA_SALES_ITEMS_IN-TARGET_QTY      = '1'.
    <br>  WA_SALES_ITEMS_IN-TARGET_QU       = 'ST'.
    <br>  WA_SALES_ITEMS_IN-SHORT_TEXT      = 'TESST AJ'.
    <br>  WA_SALES_ITEMS_IN-SALES_UNIT      = 'ST'.
    <br>  WA_SALES_ITEMS_IN-CURRENCY        = 'NOK'.
    <br>  WA_SALES_ITEMS_IN-WBS_ELEM        = '011215'.
    <br>  APPEND WA_SALES_ITEMS_IN TO LT_SALES_ITEMS_IN.
    <br>
    <br>  DATA : WA_ORDER_ITEMS_INX TYPE BAPISDITMX.
    <br>  DATA : LT_ORDER_ITEMS_INXN TYPE STANDARD TABLE OF BAPISDITMX.
    <br>  DATA : WA_ORDER_HEADER_INX TYPE BAPISDHD1X.
    <br>  DATA : LT_ORDER_HEADER_INXN TYPE STANDARD TABLE OF BAPISDHD1X.
    <br>
    <br>  WA_ORDER_ITEMS_INX-UPDATEFLAG = ' '.
    <br>  WA_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
    <br>  WA_ORDER_ITEMS_INX-MATERIAL        = 'X'.
    <br>  WA_ORDER_ITEMS_INX-TARGET_QTY      = 'X'.
    <br>  WA_ORDER_ITEMS_INX-TARGET_QU       = 'X'.
    <br>  WA_ORDER_ITEMS_INX-SHORT_TEXT      = 'X'.
    <br>  WA_ORDER_ITEMS_INX-SALES_UNIT      = 'X'.
    <br>    WA_ORDER_ITEMS_INX-WBS_ELEM   = 'X'.
    <br>
    <br>  APPEND WA_ORDER_ITEMS_INX TO LT_ORDER_ITEMS_INXN.
    <br>
    <br>  CALL FUNCTION 'SD_SALESDOCUMENT_CREATE'
      <br>   EXPORTING
    <br>     SALESDOCUMENT                 = LV_VALUE_SALESDOCUMENT
    <br>      SALES_HEADER_IN               = LT_SALES_HEADER_IN
    <br>*     SALES_HEADER_INX              =
    <br>*     SENDER                        =
    <br>*     BINARY_RELATIONSHIPTYPE       = ' '
    <br>     INT_NUMBER_ASSIGNMENT         = LV_INT_NUMBER_ASSIGNMENT
    <br>*     BEHAVE_WHEN_ERROR             = ' '
    <br>*     LOGIC_SWITCH                  = ' '
    <br>     BUSINESS_OBJECT               = ' '
    <br>*     TESTRUN                       =
    <br>*     CONVERT_PARVW_AUART           = ' '
    <br>     STATUS_BUFFER_REFRESH         = 'X'
    <br>*     CALL_ACTIVE                   = ' '
    <br>   IMPORTING
    <br>     SALESDOCUMENT_EX              = LV_SALESDOCUMENT_EX
    <br>     SALES_HEADER_OUT              = LT_SALES_HEADER_OUT
    <br>     SALES_HEADER_STATUS           = LT_SALES_HEADER_STATUS
    <br>   TABLES
    <br>     RETURN                        = LT_RETURN
    <br>     SALES_ITEMS_IN                = LT_SALES_ITEMS_IN
    <br>*     SALES_ITEMS_INX               =
    <br>     SALES_PARTNERS                = LT_SALES_PARTNERS
    <br>     SALES_SCHEDULES_IN            = LT_SALES_SCHEDULES_IN
    <br>*     SALES_SCHEDULES_INX           =
    <br>     SALES_CONDITIONS_IN           = LT_SALES_CONDITIONS_IN
    <br>*     SALES_CONDITIONS_INX          =
    <br>*     SALES_CFGS_REF                =
    <br>*     SALES_CFGS_INST               =
    <br>*     SALES_CFGS_PART_OF            =
    <br>*     SALES_CFGS_VALUE              =
    <br>*     SALES_CFGS_BLOB               =
    <br>*     SALES_CFGS_VK                 =
    <br>*     SALES_CFGS_REFINST            =
    <br>*     SALES_CCARD                   =
    <br>     SALES_TEXT                    = LT_SALES_TEXT
    <br>*     SALES_KEYS                    =
    <br>*     SALES_CONTRACT_IN             =
    <br>*     SALES_CONTRACT_INX            =
    <br>     EXTENSIONIN                   = LT_EXTENSIONIN
    <br>*     PARTNERADDRESSES              =
    <br>*     SALES_SCHED_CONF_IN           =
    <br>     ITEMS_EX                      = LT_ITEMS_EX
    <br>     SCHEDULE_EX                   = LT_SCHEDULE_EX
    <br>*     BUSINESS_EX                   =
    <br>*     INCOMPLETE_LOG                =
    <br>     EXTENSIONEX                   = LT_EXTENSIONEX
    <br>*     CONDITIONS_EX                 =
    <br>*     PARTNERS_EX                   =
    <br>*     TEXTHEADERS_EX                =
    <br>*     TEXTLINES_EX                  =
    <br>*     BATCH_CHARC                   =
    <br>*     CAMPAIGN_ASGN                 =
    <br>*     CONDITIONS_KONV_EX            =
    <br>.
    <br>
    <br> commit work.
    <br>
    <br>I am aware that there are other BAPI's available to create  a new sales order(BAPI_SALESORDER_CREATEFROMDAT2  <br>etc.) but the problem with using them is they internally call the same function module 'SD_SALESDOCUMENT_CREATE'. i  <br>have already tried to create the sales order using  'BAPI_SALESORDER_CREATEFROMDAT' but the effect is the same.
    <br>When I pass WBS element value in VA01 and create a sales order I can see that WBS element value is coming correctly.  <br>But when i create the sales order using ABAP code WBS element is coming as blank. When I execute this standard FM it  <br>creates the sales order correctly with a blank against WBS element. I checked in the VBAP table the value is not even  <br>populated there . Kindly share your valuable inputs for the same.
    - Akshay

    May be you have to post this in ABAP forum to get suitable suggestions.
    G. Lakshmipathi

  • Container Variables Not Filled

    Hi,
    I have configured Alert Category and Alert Rules to trigger exceptions at Mapping, Adapter and Proxy level.  All these alerts are getting triggered properly.  But the container variable, &SXMS_FROM_SERVICE& is not getting populated and displays the tag as such.
    I infact checked the Note 947738 (Container Element not filled).  But this is for SP 09.  We are in Release 7.0 SP 11.  So the note is already implemented.
    But still I am facing this problem.  The container variables are not filled.  Can someone suggest how to fix this.
    Regards.
    Bala

    Hi,
    Are all the other Container Variables being populated?
    If yes, one option is to check note : 913858 . This note describes one question when the From Interface Container variable does not fill up. Check what it mentions.
    Regards
    Bhavesh

  • Reg: Container elements

    Hi,
    I'm doing a bpm scenario where i recieve a file using receive step then use a switch to check if a condition satisifies based on that I'm sending to File using send step and in other block using Mail.
    Im getting error as container elements not intialized when did syntax check in bpm  and also for receive step it says container element intialized but not used,,,
    please tell me what needs to be done
    Thanks

    Hi,
    for every abstract interface you will contanier variable and this varaible will be used in BPM Steps, this i very basic fund.
    so please make sure that you have done perfectly.
    Regards,
    Raj

  • Output of multiline container element in email not working

    I'm trying to display a multiline container element in an e-mail from workflow. The element container contains 2 lines. I can see these have been populated in the log in SWIA. However, when using &ITAB##& to output these lines nothing is diplayed. I've also tried &ITAB[]& and &ITAB& all of which return no lines in the e-mail.
    Does anyone know if this is something I'm doing wrong or is there an error in R/3. I'm on release 4.6c.
    Thanks
    Karen

    This is getting annoying. This was sednging e-mails and printing the table in the e-mail fine. Then I had to add more fields to the table ITAB. After this the table wasn't showing again in the e-mail. I recreated the workflow, tasks and even the BOM, but still nothing.
    As before I can see the ITAB entries in the details of the e-mail task. But, they don't get written into the e-mail even though I'm selecting &ITAB##& from the Expressions section to put into the e-mail.
    Is there anything I haven't tried. Is there something I'm doing wrong? Is this a SAP problem that can be fixed with a note. I've had a look, but can't find anything about it.
    Thanks
    Karen

  • Container element is not being displayed in email

    Hi Experts,
      I inserted an element from container into email text as below
    The task has been pending in inbox for more than &ins_num& days.
    The value of &ins_num& in container is 9
    In output I get
    The task has been pending in inbox for more than  days.
    Please let me know what is wrong. The binding works fine. No error in workflow.
    Thanks.

    Hi Miak,
    Greetings..:-)
    > I inserted an element from container into email text as below
    > The task has been pending in inbox for more than &ins_num& days.
    > The value of &ins_num& in container is 9
    > In output I get
    > The task has been pending in inbox for more than days.
    > Please let me know what is wrong. The binding works fine. No error in workflow.
    Check on the Following things:->
    1> The Container Element has Initial Value defined, If Yes - it should symbolise in Green Colour.
         If 'Not', then check the WF Log and see whether this Container Element is fetching the Values orr   not.
    2> If the Values are not being Fetched, then the Problem lies with the Binding of these WF Containers.
    Let me know if you are still facing Issues.
    Regards,
    Kanika

  • BPM error:Container element in step transformation is not initialized

    Hello Experts,
    I am new to the concept of BPM.
    I'm trying to create an integration process in which I'm taking an Idoc and processing it in many ways. The process contains many transformation steps. There two such transformation steps which have been placed in block step in a fork. And i get this error: Container element XXX in step transformation is not initialized
    What could be the problem?
    Regards,
    Akhil

    Hi
    if u are getting the messaga with red sigh then it means it will craete the error while running the scenario.
    but if it is in blue then i think it will not create any error.
    the meaning of that statement is that the container u have defind is not used anywhere. it is just giving u a warning message.
    Thanks
    Rinku

  • Container element value does not display

    Hi,
    I am facing a strange issue.
    There is one step in my custom workflow which sends sap mail. The subject of the e-mail has a container element &notif&. When I check the workflow log this container element gets set with a value just before this step and so I expect it to be displayed in the e-mail .
    But the issue is i am getting the mail in my inbox which says ....&notif& ......
    i.e Instead of displaying the value of this container it displays the text &notif&.
    The same container element is used in the same e-mail message body where it displays correctly.
    has anyone faced this kind of an issue before?
    Thanks,
    Simmi

    Yes it is set to Expression.
    This mail step was not created from scratch.
    I just changed a few texts in the subject of this Mail step in an already existing workflow without touching the container element in the subject. But after i did this change and tested teh workflow, the container element no longer displayed any value in the subject, but it does continue to show value in the message body.
    Any suggestions to solve towards this issue will be extremely helpful.
    Thanks,
    Simmi

Maybe you are looking for