IDoc extension not passing to PI at runtime

Hello Gurus,
We have a DELVRY05 IDoc which was extended with a new segment. This has been working very well and is in our production environment. We are now in develpment with a new modification and have added two new fields to the extended segment. We are able to import the IDoc and complete the mapping changes in PI using the new fields. However, when we test the changes, we do not see the new fields being populated in the Inbound Message Payload.
I have searched through many of the existing forums which led me to perform cache updates. Still we have the issue.
We are using ECC and PI 7.0.
The new fields are visible in WE02.
The new fields do not show in the Inbound Message Payload in PI.
We have updated the following:
Java VM Cache Refresh:SLD Cache
Java VM Cache Refresh:Value Mapping Guid Cache
Java VM Cache Refresh:Value Mapping Group Cache
Java VM Cache Refresh:Value Mapping Value Cache
Java VM Cache Refresh:Cache for Softwarecomponents
Java VM Cache Refresh:Adapter metadata
Our Basis guy then did these:
Xi Data Cache Refresh: http://<system>/CPACache/refresh?mode=partial
Xi Data Cache Refresh: http://<system>/CPACache/refresh?mode=full
Any assistance that can be provided will be greatly appreciated.
Thomas

Hi,
Have you tried IDX2??
Mark the idoc type for which you have added extension and delete it.
The first time you send the idoc through it will be added to IDX2 again and have the new fields.

Similar Messages

Idoc extension not displayed - outbound / INVOIC02

Hi All,
I have created a Extension Idoc ZINV2 , Basic type INVOIC02.
I have added the segment YE1EDK01 ( with 2 custom fields ) under the segment E1EDK01. the message type is INOIC.
The Partner Type is KU and the partner number used is 7000001.
In the Outbound parameters : i have assigned
Partner function as PY
Message type is INVOIC.
Message function is US.
and I am assigning the Basic type and Extesnion type here properly.
The segment and the idoc extension are released.
In VF02 , in OUTPUT i am giving the Output type as YU10 for outout MEDIUM EDI.
The idoc is getting created without any problem. But the Extesnion type is not displayed in the idoc in WE02. the added segment YE1EDK01 is not displayed.
What could be the Problem , i am not able to sort out.
Kindly help me in solving this .
Should we need to do anything in WE57.
Kindly help in solving this problem.
Waiting for your replies.
Suki.R

Hi,
When you need to add an Idoc extension, it must be appended in INT_EDIDD itab, after the actual segment. hen only it will be picked in the Idoc.
Steps to add extension(Example)::
1. WE31 - Create A segment(ZETEST) with additional fields, that needs to be added.
2. WE20 - Create the Extension(ZORDERS) for the given Basic type.
        2.1    Now add the custom segment(ZETEST) as the child segment to the segment which you want to extend(e.g. E1EDK01)
        2.2    Define the minimum and maximum occurrence
3. Release the custom segment (ZETEST) and the Extension (ZORDERS).
4. WE82 - Assign Basic type to extension / messages
5. WE30 - Check and Transport IDoc extension
                 5.1 Give the Extension Name(ZORDERS)
                 5.2 In the menu Path : Development Object -- >Check (Ensure that there are no errors or warnings)
                 5.3 Now Transport: Path: Development -> Transport
6. WE20 - Now go to the Partner Profile and add the Extension(ZORDERS) in the Message control data and Save it.
7. Go to the Function module for processing the Idoc, and add the code for custom fields.
Eg Code:
clear: lt_dxvbep, lt_dxvbep[],
       ls_dxvbap,
       ls_ysd_tvpr,
       ls_aufk,
       ls_ze1edket,
       ls_edi_partner,
       ls_int_edidd.
if int_edidd-segnam = 'E1EDK01'.
do 1 times.
    check control_record_out-cimtyp = 'ZORDERS'.
    data: ls_pmt_vbak like vbak,
          ls_pmt_vbuk like vbuk,
          ls_e1edk01 like e1edk01,
          ls_ze1edk01 like ze1edk01,
          ls_nastflags like ysd_tvoutflags.
*/ Clear workarea
    clear: ls_pmt_int_edidd.
*/ Get data
    select single * into ls_pmt_vbak from vbak
    where vbeln = dxvbak-vbeln.
    select single * into ls_pmt_vbuk from vbuk
    where vbeln = dxvbak-vbeln.
*/ Get customizing
    select * up to 1 rows
    from ysd_tvoutflags into ls_nastflags
    where flagn = 'STA_PMT_DELETE_IDOC'
      and kappl = 'V1'.
    endselect.
*/ Set extended name
    ls_pmt_int_edidd-segnam = 'ZE1EDK01'.
*/ Set data for ZE1EDK01
    ls_ze1edk01-cmgst = ls_pmt_vbuk-cmgst.
*/ Move to EDIdata and append
    move ls_ze1edk01 to ls_pmt_int_edidd-sdata.
    append ls_pmt_int_edidd to int_edidd.
*/ Modify E1EDK01 with extra field
    loop at int_edidd where segnam = 'E1EDK01'.
      move int_edidd-sdata to ls_e1edk01.
      ls_e1edk01-lifsk = ls_pmt_vbak-lifsk.
      move ls_e1edk01 to int_edidd-sdata.
      modify int_edidd.
    endloop.
enddo.
Hope this helps........

IDOC extension not considerated

Hello.
I am having a problem with an extension. I have added in an IDOC structure of ORDERS05 an extension with a segment ZE1EDK01 that is a child of E1EDK01. I went throught all the steps we normally read on every website... the WE31 thing, the "set release" etc... In the final, when you look at the structure in WE30, the extension is found as a child of E1EDK01.
That new segment contains a KOSTL that I manually fill in the user exit EXIT_SAPLEINM_011.
Though, in this user-exit, we receive the "final structure" of the IDOC where, since it is not filled yet, the added segment ZE1EDK01 is not in the final structure so I don't understand how to insert the KOSTL in my new segment that is absent of the final IDOC structure
I thought adding the segment through an append to the table containing the IDOC structure but I fell it would kinda mess up the segment structure and/or the whole IDOC structure (The new segment not being under the E1EDK01, for example).
So I have a few ideas but no real solution...
Is that possible i'm not in the right User-Exit to add the KOSTL value in the IDOC?
Am I missing something in the configuration of that extension?
Do I have to add the new segment structure myself with an append (Or an insert) inside the final IDOC?
I'm a bit in a dead end here. Only a few hypothesis but no real answers on where to head with that.
Thank you for your help.
<removed by moderator>
Regards!
Edited by: Thomas Zloch on Nov 22, 2011 5:33 PM

You are right. Since ZE1EDK01 is your own segment, you need to insert it right below E1EDK01 to which it is a child.
IDOC_OUTPUT_ORDERS won't append and fill the ZE1EDK01 segment for you, you need to do it yourself like below. And no it won't mess up anything provided, you defined ZE1EDK01 to be a child segment of E1EDK01, following right below it in your IDoc extension definition
In user exit, EXIT_SAPLEINM_011, the code below will insert ZE1EDK01 segment right below E1EDK01, its parent.
DATA: lv_tabix TYPE sy-tabix.
DATA: ls_ze1edk01 TYPE ze1edk01.
CLEAR dint_edidd.
READ TABLE dint_edidd WITH KEY segnam = 'E1EDK01'.
IF sy-subrc = 0.
 lv_tabix = sy-tabix + 1.
 CLEAR dint_edidd.
 dint_edidd-segnam = 'ZE1EDK01'.
 ls_ze1edk01-field = 'value'. "Assign your Z segment field values here
 MOVE ls_ze1edk01 TO dint_edidd-sdata.
 INSERT dint_edidd INDEX lv_tabix.
ENDIF.

JDBC -- XI -- IDoc Scenario... IDoc Extension not being created...

Hi,
I hope you can help with this issue... I have a scenario which involves mapping to an IDoc which we have extended. From IDX5 I can see the outbound message from XI and in the XML I can see the extension segments have been properly created. But when the IDoc is posted to the destination system these segments are not there.
I have checked so far...
- The correct IDoc definition with extension has been imported
- The IDoc which is being created contains the extension in the control record
- Refreshed all caches
- Deleted and reimported IDoc metadata
If anyone has come across this issue before, please let me know...
Thanks,
Pete

Hi Pete,
Please check the Idoc receiver communication channel. Apply Control Record Values from Payload should be checked.
Thanks,
Shubhankar

IDoc Extension not getting picked up in ALE

Hi.
We have created an extension of the type BOMMAT.
We are using RBDSEBOM via SE38 to generate IDocs.
We have coded in Extension,generated a Cust Distri Model, and also the Partner Profiles.
In the Partner Profiles We have entered the basic type as well as the extension.
Still,when the break point in the enhancement is hit,the CIMTYPE field is blank.
Any help, SAP Notes will be highly appriciated!!

Hi Anup,
Please check if the extended segements and the extended idoctype is RELEASED or not..
thank you.
Reward points if found useful

Idoc Extension name not getting populated

Hi all
I have extended the idoc INVOIC02 and inside the exit- EXIT_SAPLVEDF_002, i m writing code for custom segments. Now the problem is, i am not able to see my idoc extension name in the importing parameter(CONTROL_RECORD_OUT-CIMTYP ) of the exit FM .
I have maintained the partner profile (with same extension), distribution model and WE82 config. Please let me know, any config. is required, so the extension name will get populated.
Vinoth

Hi
Check in the WE57 where Link is maintianed for Message type Idoc type and Idoc extension is attached to FUnction Module
and check the Process code.
Prabhudas

Regarding IDOC Extension

Hi Experts,
I need to Extend IDOC COND_A03 with 5 Custom feilds. This Idoc will be populating 10 tables like A932,A933,A34,A35,A36,A37....,.I need to extend in
IDOC_INPUT_COND_A through exit CALL CUSTOMER FUNCTION '002'.
Here the 3 feilds will be present in A932 table and there will be only 4 feilds in A933 table and 3 feilds will be present in A934 table and so on. I..e all the 5 custom feilds will not be present in all the tables.
How i need to build the logic so that when the data comes to that function module i need to populate only 3 feilds into A932 table and 4 feilds into A933 table and so on..
How do i need to build the logic.., to post the data when the number of fields differ from one table to the other.

ALE FUNCTION MODULE ENHANCEMENTS
Having extended the IDOC type to contain additional fields for an inbound or outbound application, you now want to enhance ALE function modules for populating the additional segment on the outbound or applying the additional segment data on the inbound application.
The core working code for ALE processes for a given application area is always encapsulated in ABAP/4 function modules. These function modules are associated with such control information as message types and process codes. So the ALE process checks this control information and derives the name of the function module to invoke for that particular IDOC processing from certain database tables. These function modules contain objects known as customer functions, which can be considered SAP Enhanced user exits. A function module is called at a particular point during the processing of the main program or function module, and it can be used to influence data processing at that point by adding code to the customer function. The customer function behaves like a normal function module and has import and export parameters, tables (internal tables) statement, and exception processing. Unlike a conventional user exit, customer functions give you the ability to modify only data available to you by the function moduleâs parameters and internal tables. While most ALE/EDI function modules are supported by customer functions, there are ALE/EDI processes that still use conventional user exits. There are a few ways to determine which function module to enhance for a given message type/process code:
For master data distribution, from SALE go to Extensions -> Master data distribution -> Setup additional data for message types. Search for message type DEBMAS in this example. You see an entry for DEBMAS associated with function module MASTERIDOC_CREATE_SMD_DEBMAS. This data is stored on table TBDME. The function module names for all master data message types follow this pattern: MASTERIDOC_CREATE_SMD_messagetype. This function module calls another function module of name MASTERIDOC_CREATE_DEBMAS or MASTERIDOC_CREATE_messagetype. Search for the words customer function, and you find several hits that can be used to add code to the function module.
From WEDI got to Control -> Inbound process codes -> Inbound with ALE service -> Processing by function module (transaction WE42), or from WEDI go to Control -> Outbound process codes -> Outbound with ALE service -> With function module (transaction WE41). There will be function modules associated with the process codes. For inbound, the function modules usually follow this pattern: IDOC_INPUT_messagetype: for example, IDOC_INPUT_CHRMAS for inbound characteristics master.
Use transaction WE57 or from WEDI go to Development -> Message/Application Object. The entries list the function module, Business Object, message type, and IDOC type that are used for inbound ALE/EDI interfaces.
Customer functions are not specific only to ALE and EDI but also to all programs/modules in SAP R/3. Customer function is a SAP enhancement component; the other two types are menu and screen enhancements.
All customer function exits are maintained in SAP enhancements and are found by using transaction SMOD. After executing transaction SMOD, pull down (F4) on the enhancement name field, and execute again. This provides you with a list of all SAP enhancements available. SAP enhancements are grouped by development class pertaining to an application area. Choose Application development R/3 SD master data distribution for development class VSV to lead to a screen that lists VSV00001 as an enhancement (see Figure 5). Press Component +/- to display its function exit components. There are four possible components listed, all of which are function exits (and are function modules) that are called from the ALE function modules in the form Call Customer Function Î001â. This is a special occurrence of the ABAP statement Call. Go to item Exit_SAPLVV01_ 001, which you need to enhance for the Customer Master outbound example of an IDOC extension. In the ALE-function module MASTERIDOC_CREATE_DEBMAS, the statement CALL Customer Function 001 is translated in the background to call component EXIT_SAPLVV01_001. Although this function exit can be edited using transaction SE37, you will use a simpler approach.
When you use SAP enhancements and their components, you manage them with an SAP object known as a project, which is like an envelope containing the selected enhancements and their components. A project can be used to control the execution of components and to transport them to other clients and instances in SAP. Basically, the process involves creating a project, including enhancements and components that are to be enhanced, editing the components, and then activating the project. The following process creates a project for our example Customer Master IDOC extension:
Execute transaction CMOD.
Enter name of project, say CSTMAST1.
Click on Create.
Enter a description of the project.
Save.
Click on SAP Enhancements.
Enter VSV00001 for Enhancement.
Save.
Once youâve created the project, edit the function exit components and activate the project. Remember that the code in the function exit enhancement will execute only if the project is activated. In fact, this is a convenient SAP enhancements feature, whereby the work in progress (developing code in the customer function) will not affect users of that application. When the code is completed, the project can be activated so the enhanced functionality takes effect. It can also be deactivated for maintenance.
As mentioned earlier, customer functions (function exits) are embedded in ALE function modules and can be used to influence the creation and modification of IDOC data on an outbound application or to post additional or modified IDOC data to an inbound R/3 application. Function exits are similar to regular function modules, with import/export parameters, tables (internal tables), and exceptions.
The two important factors to consider while developing the customer function are:
1. The point in the ALE function module where the function exit occurs
2. The data made available by the customer function that can be modified or posted to the R/3 application, based on the direction.
Because some function modules have several customer functions, it is critical to choose the function exit best suited for that particular enhancement. Do not attempt to perform activities that the function exit is not designed for. The importance of this point is illustrated by the following description of enhancing function modules for outbound and inbound ALE interfaces.
Outbound interfaces. In an outbound ALE interface you use function exits (customer functions) to populate additional segments created by an IDOC extension or to modify the existing IDOC data segments as per business requirements. Previously, you identified that enhancement VSV00001 has a component EXIT_SAPLVV01_001 (function exit), which can be used for populating the additional data segment Z1SADRX that you created in the IDOC extension ZDEBMASX (IDOC type ZDEBMASZ, based on Basic IDOC type DEBMAS02). You also learned that the ALE function module that calls this function exit is MASTERIDOC_CREATE_DEBMAS, which has a statement Call Customer Function 001.
Browse the function module MASTERIDOC_CREATE_DEBMAS using transaction SE37. You will find that this customer function is invoked for every segment of IDOC type DEBMAS02. In fact, the function exit is called soon after the creation of an existing segment has been populated with data and appended to the IDOC data table (internal table). Also, the function exit is exporting the message type, IDOC type, and the segment name and is importing the IDOC extension type. It is also passing the IDOC data internal table. This indicates that the ALE function module is allowing you to populate additional segments for every existing segment and modify the existing segmentâs data.
Letâs write ABAP/4 code to accomplish the task of populating IDOC segment Z1SADRX with a contact personâs business address:
From SE37, display function module MASTERIDOC_CREATE_ DEBMAS.
Find Customer Function 001.
Double-click on 001.
The function EXIT_SAPLVV01_001 will be displayed.
Double-click on INCLUDE ZXVSVU01.
You will be asked to create a new include object. Proceed as desired.
Enter code (as in Listing 1).
Be sure to perform a main program check (Function Module -> Check -> main program) and extended program check (Function module -> Check -> Extended check).
Now that you have extended the IDOC and enhanced the ALE function module based on the requirements for the contact personâs business address on the Customer Master, letâs test the interface. You should create a logical system and define a port for this interface. You should also configure the Customer Distribution Model to indicate that message type DEBMAS is being distributed to this logical system. The only difference in configuration between a regular outbound ALE interface and an enhanced one is the partner profile definition. While maintaining the outbound parameters of the partner profile, make sure the IDOC type is ZDEBMASZ. The fields for Basic IDOC type and extension type are automatically populated with DEBMAS02 and ZDEBMASX, respectively.
To maintain the contact personâs business address of a customer:
Use transaction BD12 or from BALE go to Master Data ->Customer -> Send and send that Customer Master record by executing the transaction after filling in the relevant fields such as customer number, message type, and logical system.
Use transaction WE02 or WE05 to verify the IDOC created. You should see the new segment Z1SADRX populated with the correct data.
With SAP releases below 4.5B, you cannot capture changes to business address through change pointers because a change document object is not available for capturing business address changes, and also earlier releases have not been configured to write change documents for a contact personâs business address. If you would like this functionality, you can either create change document objects, generate function modules to create change documents, and perform ALE configuration to tie it in, or make a cosmetic change to the contact person screen data while changing the contact personâs business address so that it gets captured as a change to the Customer Master. Subsequently, the ALE enhancement that you performed captures the contact personâs business address.
Inbound interfaces. The process for enhancing inbound ALE interfaces is similar for outbound, with a few exceptions; specifically in the coding of customer functions (function exits) for the ALE/EDI function modules.
The first step is to create an IDOC extension for the specific Basic IDOC type by adding new segments at the appropriate hierarchy level: that is, associated to the relevant existing segment. Populate the data fields on the new segments with application data by the translator or external system/program before importing them into the R/3 System. Then, find the ALE function module that is invoked by the inbound processing. By browsing through the code or reading the documentation on the function exit enhancements using the SMOD transaction, identify the function exit in which you should place your code. The technique used in the code to post the additional or modified IDOC data to the application can vary based on the application rules and requirements, the data available at that point in processing, and the application function modules available to update the application tables. It is important to search first for application modules that process the data and see if they can be called within the function exit. If the additional data in the extended segments in specific to a custom table or resides in nonkey fields of a single or small set of tables, you may be able to update it directly by SQL statements in the function exit. This approach should be carefully evaluated and is certainly not highly recommended.
Another option is to use Call Transaction from within the function exit to process the additional data. For example, in the case of message type WMMBXY for inbound goods movements from a warehouse management system, the standard interface creates batches for materials, but does not update its characteristics. In such a case, you can use Call Transaction MSC1 to create the batch and assign characteristic values to it from within the function exit provided.
regards,
srinivas
*reward for useful answers*

Not able to set Weblogic Runtime on eclipse while adding new weblogic srvr

Hi Everyone,
I downloaded Oracle Integration pack for eclipse by clicking at "Download additional server adapters". I am not able to set Weblogic Runtime on eclipse while adding new weblogic server.
I am trying to give following values:
Name :Oracle WebLogic Server 10gR3 (2)
Weblogic home :C:\bea\wlserver_10.3
Java home: C:\bea\jrockit_160_05
Below it I am getting "No applicable extension found" and finish button is greyed out.
Please help in telling what is wrong. Never faced such an issue.
Thanks
SM

I found this problem too.
OS:windows7、eclipse:helios、oepe:Part of Oracle Enterprise Pack for Eclipse 11.1.1.7.3
<workspace>\.metadata\.log:
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: enter_new_hit_count in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: exception_occurred_setting_bp_properties in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: hit_count_must_be_positive in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: no_description_provided in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: scripts in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: select_javascript_file in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: set_bp_hit_count in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: suspend_target in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: suspend_thread in: org.eclipse.wst.jsdt.debug.internal.ui.messages
!ENTRY org.eclipse.osgi 2 1 2012-06-05 00:16:06.357
!MESSAGE NLS unused message: the_argument_0_is_not_valid in: org.eclipse.wst.jsdt.debug.internal.ui.messages
I tried the weblogic 10.3.1、10.3.3、10.3.4、10.3.5 still show the info that "No applicable extension found" and finish button is greyed out.
What is the reason?
thanks!

When using pop up editor windows on a Joomla 1.0.15 website the URLs selected in the pop-up are not passed back to the main window

The Joomla content management system version 1.0.15 provides a content editor which uses pop-up windows to select images and files. When using any of these pop up editor windows since 3.6.9 the URLs selected in the pop-up are not passed back to the main editor window.
Up until FF 3.6.8 there were no problems, but FF 3.6.9 and 3.6.10 both exhibit this same problem, as does FF 4 Beta 6. (Support Question raised on this forum in early September when 2.6.9 was released but no response)

Do you have that problem when running in the Firefox SafeMode?
[http://support.mozilla.com/en-US/kb/Safe+Mode]
''Don't select anything right now, just use "Continue in SafeMode."''
If not, see this:
[http://support.mozilla.com/en-US/kb/troubleshooting+extensions+and+themes]

Find Idoc extension type for Basic Idoc type

Hi all,
Is there any way to find existing extesions for Idoc given by SAP? For example, for basic idoc DEBMAS05 for version 4.7 , Idoc extension is DEBMASEXT.
In similar way I want to know what is Idoc extension for Idoc basic type PREQCR02 [Create Purchase Requisition].
Thanks in advance.
Madhura

The reason is preqcr02 is a generated idoc type and matmas05 and debmas05 are not generated idoc types .
You can search in table EDBAS for this . If you go for dynamic debuggin , message comes from form
create_ext_structure in include MSED5F02
data: l_edbas type edbas.
select single * from edbas into l_edbas
     where idoctyp eq edi_iapi01-idoctyp.
if l_edbas-generated eq 'X'.
   message e099(b1) with
      'Action is not possible for generated idoctypes'.
endif.
Edited by: anil sasidharan on Feb 25, 2009 12:51 PM
Edited by: anil sasidharan on Feb 25, 2009 12:59 PM

Values not passing from form to context attributes (value attributes)

Hi Experts,
I have bound the properties of theadobe interactive form (WD-Java) to the context attributes but the values are not passing to the value attributes at runtime.
For your information I have not bound the pdfsource binary attribute of the view to the custom controller pdfsource binary attribute.
Please advise.
Thanks,
Shobhit

Context
   GetData - ModelNode mapped to controller context (DataSource)
         Attribute1 - Value Attribute (Form Field)
Is it allright to have the Data Source as a ModelNode (mapped to the controller context node) and then have Value Attributes under the ModelNode which are then bound to the adobe form input fields.
I know its frustrating to advise on such questions without looking at the code actually. But I would definitely need your support.
If possible could you mail me a project of yours where you have the form being PREFILLED with some values coming from a RFC FM and then the same form gets posted to SAP though another RFC FM.
Thanks,
[email protected]
OK. When I create a Fresh Adobe Interactive Form application, it works fine.
The problem Im facing is in the case, when Im using an existing PDF file created in the ABAP stack (TCode SFP). I am importing this PDF file into the WebDynpro Java Application and then binding the fields. So in this case the context binding does not work.
You guyz are right, I need to check if there is any other script which exists. But still what are views after this update?
Message was edited by:
        Shobhit Swarup Mathur

AP 1231G Not Passing DHCP to clients

Hello My company AP 1231G is not passing the DHCP address to the client from the DHCP server can you please advise on my config listed below
basicly the AP is on its own VLAN 10.1.123.1 and the DHCP server is 10.1.10.2 -- trying to use iphelper to pass DHCP to clients and the AP is on static IP 10.1.123.2--
! Last configuration change at 13:15:56 +0800 Fri May 25 2012 by root
! NVRAM config last updated at 13:15:56 +0800 Fri May 25 2012 by root
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname XXXXXXXXXX
clock timezone +0800 8
ip subnet-zero
no ip domain lookup
ip domain name XXXXXXXXXXXXX
aaa new-model
aaa authentication login default local
aaa authorization exec default local
aaa session-id common
dot11 syslog
dot11 ssid XXXXXXXXXX
   authentication open
   authentication key-management wpa
   guest-mode
   infrastructure-ssid optional
   wpa-psk ascii XXXXXXXXXXXXXXXXXXXXXXX
dot11 arp-cache optional
username root privilege 15 password XXXXXXXXXXXXXXXXXXXXX
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption mode ciphers aes-ccm tkip
ssid XXXXXXXXXXX
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
no preamble-short
channel 2432
station-role root access-point
no dot11 extension aironet
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled
interface FastEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface BVI1
ip address 10.1.123.2 255.255.255.0
ip helper-address 10.1.10.2
ip default-gateway 10.1.123.1
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
access-list 111 permit tcp any any neq telnet
snmp-server view dot11view ieee802dot11 included
snmp-server view ieee802dot11 ieee802dot11 included
snmp-server community public RO
snmp-server community private view undefined RW
bridge 1 route ip
line con 0
terminal-type teletype
line vty 0 4
terminal-type teletype
sntp server 114.80.81.13
sntp broadcast client
end

Roan:
Where is your DHCP server configured (swtich, firewall, 3rd party server..etc)?
Does it work correctly if the AP IP on same subnet and ip-helper is not being utilized?

IDOCS Error - Not getting processed automatically

Hi All,
We are loading hierarchy for a Product from R/3 system using the standard datasource.
When we execute the info package, IDOCs are not getting processed automatically.
We are facing the below error message.
Error when updating Idocs in Business Information Warehouse
Diagnosis
Errors have been reported in Business Information Warehouse during IDoc update:
No status record was passed to ALE by the applicat
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
Thanks in Advance
Regards,
Sachin

Hi,
This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
Hope it helps a lot.
Thanks and Regards,
Kamesham

IDOC: Problem with data filter for IDOC extension field

Hallo!
I've created an idoc extension for the basic type DEBMAS06 that works fine. Now I want to use a data filter for one field ( company code ) of my segment. Every segment with a company code different from 100 should be filtered and not send to the other client. But what happend is that for all customers that have at least one company code different from 100, all segments including the one with cc 100 were deleted and a error "Segment ... does not exist for message type DEBMAS" appeared on the screen.
Does anyone have any ideas about this problem?

Not sure about changes to be made at the filtering options.
An alternative would be sending the data to XI as it is and perform the mapping to remove the unnecessary segments.
Disadvantage: Unnecessary processing of segment would be done at XI.
Advantage: The integration logic would be completely handled by XI.
Regards,
Prateek

Value not passing urgent

data:l_lotno like /JJVC/ERR851-master_lot_num,
 l_batno like mchb-charg.
loop at i_inv_data into wa_inv_data.
 l_batno = wa_inv_data-charg+0(1).
 if l_batno ca SY-ABCDE.
 translate l_batno to upper case.
 l_lotno = wa_inv_data-charg.
 perform f_idoc_851.
 perform f_idoc_52 .
 perform f_idoc850.
 else.
 if wa_inv_data-charg na SY-ABCDE
 and wa_inv_data-werks eq c_us11.
 l_lotno = wa_inv_data-charg+0(6).
 perform f_idoc_851.
 perform f_idoc_52 .
 perform f_idoc850.
 endif.
 endif.
endloop.
data:l_lotno like /JJVC/ERR851-master_lot_num,
 l_batno like mchb-charg.
IF p_werks EQ c_us11.
 SELECT a~docnum "doc number
 b~credat "creation date
 b~status "status of idoc
 b~statxt "last error message
 FROM /jjvc/err851 AS a INNER JOIN edids AS b
 ON adocnum = bdocnum
 INTO TABLE i_idoc_error
 WHERE a~master_lot_num eq l_lotno
 AND werks EQ p_werks.
 IF sy-subrc <> 0.
 ENDIF.
the data in l_lotno and l_batno is not passing from the above if condition to the select statement can any one help me in this.

You have to declare the l_lotno and l_batno as global variables.
here they are local variables and their scope is withing the block in which they are defined.
Declare them outside the blocks(Performs etc)
Regards,
Ravi

IDoc extension not passing to PI at runtime

Similar Messages

Maybe you are looking for