Forcing Generation of Triggers

Hi,
I need to let "forms generator" generate the DEFAULT_WHERE clause which is inserted into PRE-QUERY trigger of a given data block.
I couldn't find a way to force designer to generate this code. Anyone know how to do?
Designer Release is 9.0.4.5

Have you set Query WHERE/VALIDATION condition in a Table usage property pallette ? Also Query property of module component must be set to Yes.
I hope this will be a little help for you.

Similar Messages

Force refresh, only triggers complete refresh PI

Hello everyone,
I have a question regarding the usage of the "Force Refresh" option when running mSync (Oracle Lite 10.3.0.1). We have a publication that consists of both complete and fast refresh publication items. Whenever we run a mSync with the "Force Refresh" option enabled, we observe in webtogo that only the complete refresh publication items will be refreshed. Based on the documentation I'm expecting that all publication items should be refreshed. Is this a correct assumption? If so, do I have to make some changes to specific settings to enable synchronization of all publication items, or did I ran into a bug ?
Thanks in advance
Patrick

What do you see in the sync log when doing a force refresh?
you should see all publication items downloaded with the correct number of records. the complete refresh items should show
Complete refresh. Cause :: PubItem_mode=complete refresh
the fast refresh should show CRR
When you said a user did a rebuild and got the same behaviour, do you mean that the fast refresh publication items were
a) there with all of thier data
b) tables there, but no data
c) not there at all
if a, then force refresh should work
if b, then probably an issue with data subsetting or instantiation
if c, then check c$all_client_items and see if they appear in the list, and check the instantiated flag in data synchronisation>repository>publications>users. If not instantiated, you may not get all of the data
if there are objects missing from c$all_client_items, try a cut, paste and save on a data subsetting value for the user as that should reset the user

Why wlappc ANT task forces aways the generation of the EJB classes ?

I've got a problem with the ANT task "wlappc" witch interfaces Weblogic compilator.
In fact, I would like to execute the ebj compilation only when needed (if the deployment descriptor or a class changed for example).
It seems that this is the default behavior and the 'forcegeneration' option of the wlappc Ant task can change it (the doc is below).
forceGeneration :
Forces generation of EJB and JSP classes. Without this flag, the classes will not be regenerated unless a checksum indicates that it is necessary.
So I wrote :
<wlappc source="${descriptors}/CommandeEntities" output="${build}/CommandsEntities.jar" keepgenerated="true" verbose="true" forcegeneration="false">
<classpath refid="ejb.classpath"/>
</wlappc>
but I got the folowing result :
ejbjar:
[wlappc] Warning, output location exists H:\devWv2\wv2\build\CommandesEntities.jar
[wlappc] Created working directory: C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [VersionHelper] Recompiling because no previous hashes found
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compliance Checker said bean was compliant
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb WCritereListeMulticritere
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\WCritereListeMulticritere_u6449c_ELOImpl.java]
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Bean Sources
[wlappc] 18 sept. 2008 11:22:59 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating source for ejb Document
[wlappc] 18 sept. 2008 11:23:00 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generated the following sources for this EJB: [C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_LocalHomeImpl.java, C:\DOCUME~1\vdoneva\LOCALS~1\Temp\appcgen_1221729775921_CommandesEntities\com\experian\wv2\db\Document_6vm6yi_ELOImpl.java]
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Generating Persistence Sources
[wlappc] 18 sept. 2008 11:23:02 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Compiling EJB sources
[wlappc] Note: Some input files use unchecked or unsafe operations.
[wlappc] Note: Recompile with -Xlint:unchecked for details.
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Recompilation completed
[wlappc] 18 sept. 2008 11:23:10 weblogic.diagnostics.debug.DebugLogger debug
[wlappc] FIN: [EJBCompiler] Rmic completed
[wlappc] Compilation completed successfully.
[jar] Updating jar: H:\devWv2\wv2\build\CommandesEntities.jar
BUILD SUCCESSFUL
All the classes witch hasn't changed has been checked and regenerated. The compliler says "Recompiling because no previous hashes found".
But why ? It could be besause it creates a different working directory each time I execute this ant task ? Is this working directory configurable ?
Would you have any idea of what's happening ?
Thanks.

You can find this in the 'org\apache\tools\ant\taskdefs\defaults.properties'
file of %wl-home%\server\lib\ant\ant.jar
--Sathish
<Michael Lee> wrote in message news:[email protected]..
I mean the definition of "wlappc" not the help for wlappc???thx.
i.e.
where can i find the sentence list below:
<taskdef name="wlappc" classname="weblogic.ant.taskdefs.j2ee.Appc"/>
I mean which files this "taskdef" is being in .

Concurrent mode failure triggered by a full permanent generation?

Hello
I've read various forum posts and blogs on concurrent mode failures and I'm aware why such failures occur (small old gen, promotion guarantee failure, fragmentation) in the old gen and some options (increase heap size/old gen, use CMSInitiatingFraction, explicit System.gc() at quiet hours for compaction, etc.) that may be used to alleviate the problem. In fact, thanks to these forums, I used some of these options to effectively deal with concurrent mode failures on a SPARC system (Solaris 9). However, with my current JVM tuning exercise, the following GC log snippet from a JVM 1.4.2_10 running on HP-UX 11.23 (ia64) leaves me in doubt.
346179.949: [GC 346179.950: [ParNew: 419022K->27014K(491520K), 0.1540543 secs] 976980K->585383K(1474560K), 0.1542645 secs]
346444.644: [GC 346444.645: [ParNew: 420230K->420230K(491520K), 0.0000416 secs]346444.645: [CMS (concurrent mode failure)[Unloading class sun.reflect.GeneratedMethodAccessor1107]
[Unloading class sun.reflect.GeneratedMethodAccessor1087]
[Unloading class org.springframework.ejb.support.AbstractJmsMessageDrivenBean]
[Unloading class sun.reflect.GeneratedConstructorAccessor552]
...#lots of classes unloaded here#
[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor155]
: 558369K->317371K(983040K), 9.5144462 secs] 978599K->317371K(1474560K), 9.5147394 secs]
346677.529: [GC 346677.530: [ParNew: 393216K->13960K(491520K), 0.2163942 secs] 710587K->331331K(1474560K), 0.2166204 secs]
JVM 1.4.2_10 Flags: -Xms1536m -Xmx1536m -Xmn576m -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:MaxTenuringThreshold=31 -XX:TargetSurvivorRatio=80 -XX:SurvivorRatio=4 -XX:+TraceClassLoading -XX:+TraceClassUnloading -XX:+DisableExplicitGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xverbosegc:file=.....
Question: When using CMS, perm gen collection is turned off by default and a serial Full GC collects the perm gen. Could this have led to the concurrent mode failure seen above causing classes to be unloaded? i.e. when CMS collector needs to clean up perm gen via a serial STW GC, it generates a concurrent mode failure?
I doubt the concurrent mode failure could be caused by a full promotion guarantee failure or fragmentation given the available free heap and the fact that this was the first GC in the old generation since server startup.
Note: We do have a perm gen memory leak caused by spring/CGLIB. While we are fixing the class loading issue, we increased MaxPermSize from 256m to 512m to buy some time. With MaxPermSize=512m and -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled, we had very frequent CMS GCs (every 5 seconds) and I read that this happens because the CMSInitiatingthreshold is the same for both old gen and perm gen. So, we removed -XX:+CMSPermGenSweepingEnabled -XX:+CMSClassUnloadingEnabled and the CMS GCs are no longer frequent.
Thanks
Edited by: cybergavin on Dec 28, 2009 12:09 AM

Hmm..I think I was a bit hasty there...
[ParNew: 420230K->420230K(491520K), 0.0000416 secs]346444.645: [CMS (concurrent mode failure)[Unloading class........ indicates a parallel scavenge could not be performed most probably due to a "young generation guarantee" failure. Also, HPjmeter revealed no issues with perm gen growth. So, I have decreased the size of the young generation and triggered CMS earlier (changes in bold below):
*JVM 1.4.2_10 Flags:* -Xms1536m -Xmx1536m *-Xmn512m* -XX:PermSize=512m -XX:MaxPermSize=512m -XX:+UseConcMarkSweepGC -XX:MaxTenuringThreshold=31 -XX:TargetSurvivorRatio=80 -XX:SurvivorRatio=4 -XX:+TraceClassLoading -XX:+TraceClassUnloading -XX:+DisableExplicitGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps *-XX:CMSInitiatingOccupancyFraction=50 -XX:+UseCMSInitiatingOccupancyOnly* -Xverbosegc:file=.....
Will post back on results of the above....

ALE interface generation from BAPI_POEC_CREATE

Hi,
I want to generate an ALE interface from BAPI_POEC_CREATE (object type BUS2201).
FUNCTION BAPI_POEC_CREATE.
*"*"Lokale Schnittstelle:
*" IMPORTING
*"     VALUE(I_PO_HEADER) LIKE BAPI_PO_HEADER_C STRUCTURE
*"        BAPI_PO_HEADER_C
*"     VALUE(I_PO_HEADER_CUST) LIKE BAPI_PO_HEADER_CUST_C STRUCTURE
*"        BAPI_PO_HEADER_CUST_C OPTIONAL
*"     VALUE(I_TESTRUN) TYPE BBPS_BAPI2091-TESTRUN DEFAULT SPACE
*" EXPORTING
*"     VALUE(E_PO_HEADER) TYPE BAPI_PO_HEADER_D
*"     VALUE(E_PO_HEADER_CUST) TYPE BAPI_PO_HEADER_CUST_D
*" TABLES
*"      I_PO_ITEMS STRUCTURE BAPI_PO_ITEM_C OPTIONAL
*"      I_PO_ITEMS_CUST STRUCTURE BAPI_PO_ITEM_CUST_C OPTIONAL
*"      I_PO_ACCASS STRUCTURE BAPI_ACC_C OPTIONAL
*"      I_PO_ACCASS_CUST STRUCTURE BAPI_ACC_CUST_C OPTIONAL
*"      I_PO_PARTNER STRUCTURE BAPI_BUP_C OPTIONAL
*"      I_PO_TEXT STRUCTURE BAPI_TEXT_I OPTIONAL
*"      I_PO_ATTACH STRUCTURE BAPI_ATT_C OPTIONAL
*"      I_PO_ORGDATA STRUCTURE BAPI_ORG_C OPTIONAL
*"      I_PO_LIMIT STRUCTURE BAPI_LIMIT_C OPTIONAL
*"      I_PO_SDLN STRUCTURE BAPI_SDLN_C OPTIONAL
*"      E_PO_ITEMS STRUCTURE BAPI_PO_ITEM_D OPTIONAL
*"      E_PO_ITEMS_CUST STRUCTURE BAPI_PO_ITEM_CUST_D OPTIONAL
*"      E_PO_ACCASS STRUCTURE BAPI_ACC_D OPTIONAL
*"      E_PO_ACCASS_CUST STRUCTURE BAPI_ACC_CUST_D OPTIONAL
*"      E_PO_PARTNER STRUCTURE BAPI_BUP_D OPTIONAL
*"      E_PO_ORGDATA STRUCTURE BAPI_ORG_D OPTIONAL
*"      E_PO_LIMIT STRUCTURE BAPI_LIMIT_D OPTIONAL
*"      E_PO_SDLN STRUCTURE BAPI_SDLN_D OPTIONAL
*"      E_PO_TEXT STRUCTURE BAPI_TEXT_I OPTIONAL
*"      E_PO_STATUS STRUCTURE BAPI_BBP_STATUS OPTIONAL
*"      E_PO_ATTACH STRUCTURE BAPI_ATT_D OPTIONAL
*"      RETURN STRUCTURE BAPIRET2 OPTIONAL
1) I encoutered a first problem : as you can see, these are two parameters with the same type BAPI_TEXT_I. So it gives an error message during generation in BDBG. I can bypass this error by deleting the second parameter (E_PO_TEXT) in debug. But I don't like this method of course...
2) I have a second problem : the three parameters I_PO_HEADER_CUST, I_PO_ITEMS_CUST, I_PO_ACCASS_CUST are not taken in account in the generated FM (ZIDOC_INPUT_ZPURCHASEORDEREC_C), even if corresponding EDI segments are generated. I needed to add them manually (at the end of the following code) :
FUNCTION zidoc_input_zpurchaseorderec_c.
*"*"Interface locale :
*" IMPORTING
*"     VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
* this function module is generated                                   *
*          never change it manually, please!        10.06.2008         *
DATA:
      z1zpurchaseorderec_create LIKE z1zpurchaseorderec_create,
      z1bp_po_header_c LIKE z1bp_po_header_c,
      z1bp_po_item_c LIKE z1bp_po_item_c,
      z1bp_acc_c LIKE z1bp_acc_c,
      z1bp_bup_c LIKE z1bp_bup_c,
      z1bp_bup_c1 LIKE z1bp_bup_c1,
      z1bp_bup_c2 LIKE z1bp_bup_c2,
      z1bp_text_i LIKE z1bp_text_i,
      z1bp_att_c LIKE z1bp_att_c,
      z1bp_org_c LIKE z1bp_org_c,
      z1bp_limit_c LIKE z1bp_limit_c,
      z1bp_po_item_d LIKE z1bp_po_item_d,
      z1bp_po_item_d1 LIKE z1bp_po_item_d1,
      z1bp_acc_d LIKE z1bp_acc_d,
      z1bp_bup_d LIKE z1bp_bup_d,
      z1bp_bup_d1 LIKE z1bp_bup_d1,
      z1bp_bup_d2 LIKE z1bp_bup_d2,
      z1bp_org_d LIKE z1bp_org_d,
      z1bp_limit_d LIKE z1bp_limit_d,
      z1bp_bbp_status LIKE z1bp_bbp_status,
      z1bp_att_d LIKE z1bp_att_d,
* go through all IDocs                                                 *
LOOP AT idoc_contrl.
*   select segments belonging to one IDoc                              *
    REFRESH t_edidd.
    LOOP AT idoc_data WHERE docnum = idoc_contrl-docnum.
      APPEND idoc_data TO t_edidd.
    ENDLOOP.
*   through all segments of this IDoc                                  *
    CLEAR error_flag.
    REFRESH bapi_retn_info.
    CATCH SYSTEM-EXCEPTIONS conversion_errors = 1.
      LOOP AT t_edidd INTO idoc_data.
        CASE idoc_data-segnam.
          WHEN 'Z1ZPURCHASEORDEREC_CREATE'.
            z1zpurchaseorderec_create = idoc_data-sdata.
            MOVE z1zpurchaseorderec_create-i_testrun
              TO i_testrun.
          WHEN 'Z1BP_PO_HEADER_C'.
            z1bp_po_header_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_header_c
               TO i_po_header.                              "#EC ENHOK
            IF z1bp_po_header_c-doc_date
               IS INITIAL.
              CLEAR i_po_header-doc_date.
            ENDIF.
            IF z1bp_po_header_c-pcdat_to
               IS INITIAL.
              CLEAR i_po_header-pcdat_to.
            ENDIF.
            IF z1bp_po_header_c-vper_start
               IS INITIAL.
              CLEAR i_po_header-vper_start.
            ENDIF.
            IF z1bp_po_header_c-vper_end
               IS INITIAL.
              CLEAR i_po_header-vper_end.
            ENDIF.
          WHEN 'Z1BP_PO_ITEM_C'.
            z1bp_po_item_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_c
               TO i_po_items.                               "#EC ENHOK
            IF z1bp_po_item_c-deliv_date
               IS INITIAL.
              CLEAR i_po_items-deliv_date.
            ENDIF.
            APPEND i_po_items.
          WHEN 'Z1BP_ACC_C'.
            z1bp_acc_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_acc_c
               TO i_po_accass.                              "#EC ENHOK
            APPEND i_po_accass.
          WHEN 'Z1BP_BUP_C'.
            z1bp_bup_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_c
               TO i_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_C1'.
            IF sy-subrc <> 0.
              APPEND i_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_C1'.
            z1bp_bup_c1 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_c1
               TO i_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_C2'.
            IF sy-subrc <> 0.
              APPEND i_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_C2'.
            z1bp_bup_c2 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_c2
               TO i_po_partner.                             "#EC ENHOK
            APPEND i_po_partner.
          WHEN 'Z1BP_TEXT_I'.
            z1bp_text_i = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_text_i
               TO e_po_text.                                "#EC ENHOK
            APPEND e_po_text.
          WHEN 'Z1BP_ATT_C'.
            z1bp_att_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_att_c
               TO i_po_attach.                              "#EC ENHOK
            APPEND i_po_attach.
          WHEN 'Z1BP_ORG_C'.
            z1bp_org_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_org_c
               TO i_po_orgdata.                             "#EC ENHOK
            APPEND i_po_orgdata.
          WHEN 'Z1BP_LIMIT_C'.
            z1bp_limit_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_limit_c
               TO i_po_limit.                               "#EC ENHOK
            APPEND i_po_limit.
          WHEN 'Z1BP_PO_ITEM_D'.
            z1bp_po_item_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_d
               TO e_po_items.                               "#EC ENHOK
            IF z1bp_po_item_d-deliv_date
               IS INITIAL.
              CLEAR e_po_items-deliv_date.
            ENDIF.
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_PO_ITEM_D1'.
            IF sy-subrc <> 0.
              APPEND e_po_items.
            ENDIF.
          WHEN 'Z1BP_PO_ITEM_D1'.
            z1bp_po_item_d1 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_d1
               TO e_po_items.                               "#EC ENHOK
            APPEND e_po_items.
          WHEN 'Z1BP_ACC_D'.
            z1bp_acc_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_acc_d
               TO e_po_accass.                              "#EC ENHOK
            APPEND e_po_accass.
          WHEN 'Z1BP_BUP_D'.
            z1bp_bup_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_d
               TO e_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_D1'.
            IF sy-subrc <> 0.
              APPEND e_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_D1'.
            z1bp_bup_d1 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_d1
               TO e_po_partner.                             "#EC ENHOK
            READ TABLE t_edidd TRANSPORTING NO FIELDS WITH KEY
                         segnam = 'Z1BP_BUP_D2'.
            IF sy-subrc <> 0.
              APPEND e_po_partner.
            ENDIF.
          WHEN 'Z1BP_BUP_D2'.
            z1bp_bup_d2 = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bup_d2
               TO e_po_partner.                             "#EC ENHOK
            APPEND e_po_partner.
          WHEN 'Z1BP_ORG_D'.
            z1bp_org_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_org_d
               TO e_po_orgdata.                             "#EC ENHOK
            APPEND e_po_orgdata.
          WHEN 'Z1BP_LIMIT_D'.
            z1bp_limit_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_limit_d
               TO e_po_limit.                               "#EC ENHOK
            APPEND e_po_limit.
          WHEN 'Z1BP_BBP_STATUS'.
            z1bp_bbp_status = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_bbp_status
               TO e_po_status.                              "#EC ENHOK
            APPEND e_po_status.
          WHEN 'Z1BP_ATT_D'.
            z1bp_att_d = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_att_d
               TO e_po_attach.                              "#EC ENHOK
            APPEND e_po_attach.
*** JSE 12/06/08 segments "forgotten" by BDBG
          WHEN 'Z1BP_PO_HEADER_CUST_C'.
            z1bp_po_header_cust_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_header_cust_c
              TO i_po_header_cust_c.
          WHEN 'Z1BP_PO_ITEM_CUST_C'.
            z1bp_po_item_cust_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_po_item_cust_c
               TO s_po_items_cust.                          "#EC ENHOK
            APPEND s_po_items_cust TO i_po_items_cust.
          WHEN 'Z1BP_ACC_CUST_C'.
            z1bp_acc_cust_c = idoc_data-sdata.
            MOVE-CORRESPONDING z1bp_acc_cust_c
               TO s_po_accass_cust.                         "#EC ENHOK
            APPEND s_po_accass_cust TO i_po_accass_cust.
*** JSE 12/06/08
        ENDCASE.
      ENDLOOP.
    ENDCATCH.
As for first point, I don't like this method, because it modifies a generated FM. Is there a way to force generation of this 3 parameters by BDBG ?
3) Considering the risk of overwriting modications in the generated FM, I have these questions : when are regenerated interfaces created by BDBG ? Are they regenerated always manually ? Or are they regenerated during transport for example ?
Thanks a lot for your help.
Julien.

Hi,
Pls see this very useful thread:
Re: 'BAPI_POEC_CREATE' function doesn't work with extended classic scenario
BR,
Disha.
Do reward points for useful answers.

Error when activating Order Data Type ORDR

Hi all
We were activating all the ODM components acc to note 1178483 and got the following error when trying to activate Order Data Type ORDR:
Parameter CONFSTAT in access path TSTP of order data type ORDR unknown (/SCMB/ODM_ORDTYPE043)
Do any of you know what is triggering this error?
In order to carry on we removed the CONFSTAT entry and were then able to activate ORDR afterwards. However, we would like to know what the consequences are (if any) of this action.
Thank you in advance.
Best regards,
Dan Bruun

Hello Dan,
First of all you should not remove any SAP standard entry (without advice of any experts.) so now you won't get any support from SAP for this issue.
ODM activation require for creation of tables(which stores transactional data) in each client.
CONFSTAT is a field in /1OM/ORDROEHD<Your_client_number> table which stores data about PO/RO confirmation status.
You got this error because of ODM component OEHD was not activated properly.(Even it shows warning/error while component activation but it is not activated properly).
As you have removed CONFSTAT entry system won't behave normally for PO/RO creation/change/confirmation.
What you can do now restore your back-up before deletion of this entry try to do ODM activation again if you still get error then try to do force ODM activation(transaction code:/N/SCMB/ODM_GEN_ORC also checked Force Genration check box).
Even after force generation of ODM gives you error raised an OSS with SAP support for resolution.
Regards,
Nikhil

Basic Invoicing Question

Hello SD Gurus,
I have a basic question about customer invoice. I have been in sales for about five years but new to SAP. I was reading through some documentation on how to post invoices. But the way I have always seen it done in an organization is employees place orders. then the order ships, and its invoiced automatically. invoice is never manually entered, order is! Any insight would be appreciated?

Hi Zack,
your understanding is correct.The cycle starts from an order/contract placed by customer to sales executive.Once order is being captured all the organization validations (which are customized in SAP basis the organization requirements) comes in to force and a valid order can only be saved.
Saving an order is kind of acceptance as well as a trigger point for inventory planning (if ATP check is activated).The order includes following basic paarmeters:
1.Who is customer and where to ship
2.Which material is being demanded and its availbility on desired delivery date
3.Statutory Taxation & other commercial/excise taxes applicable.
4. Collection and realization period
Once order is completed , the organization plans to ship the material and than comes in picture the inventory availabilty (physical) and logistics arrangement planning.
The invoice is raised one consignment is ready for despatch for all practical purpose as if material taxable you can not issue it to customer without a valid tax/retail invoice.
The Invoice generation also triggers the accouting entry basis which collection activity is done.
Hope I,m able to clarify the SAP step linkage to practical scenrio.
Regards
Sanjay

How to call a RFC of a remote system from an ABAP webdynpro component

Dear Experts,
I am a newbie in ABAP Webdynpro.
I am working on a requirement where I have a webdynpro component on ECC system.I need to call a RFC located on CRM system from my webdynpro component on the ECC system.
How do I do that ?? Please help.
Regards,
Mamai.

Calling RFC from some other system is same as local except the difference is that you have to give destination name while calling.
And the regarding the method of calling it depends on your FM.
if it is big RFC with complex structure, you can create the service call for it with destination given as RFC desitination.
if it is simple straight forward RFC you can directly call it.
for creating RFC service call call use this method
1. Starting the Wizard
To start the wizard, position the cursor on the Web Dynpro component to be edited in the object list at the left margin of the
workbench window. Open its context menu and choose the entry Create->Service Call. The wizard is started and leads you
through the creation process.
Press Continue.
2. Choice of Controller
On the second dialog window of the wizard, you can choose whether the service call is to be embedded in an existing
controller or whether a new controller is to be created for this purpose. Service calls can only always be embedded in
global controllers u2013 that is, in the component controller or in additionally created custom controllers. It is not possible, to
embed service calls in view controllers.
a. Select radio button Use Existent Controller
b. Do not change the default entry for component: <CC name>
c. Enter for controller COMPONENTCONTROLLER
d. Press Continue.
3. Service Type and Service Selection
a. You now select, which service type should be used for this service call. Select radio button Function Module. Fill the
destination here. Press Continue.
b. Select the service: for Function Module enter <RFC name>. Press Continue.
4. The Required Methods and Context Elements
On the two subsequent dialog windows, default values are listed for giving names to the context nodes and attributes
required by the service call as well as to the required methods. The proposed names are based on the names of the
embedded service, but you can change them as required. However, heed the respective notes in the corresponding dialog
box.
a. Adapt Context: Select from Nodes/Attributes . Press Continue.
b. Specify Method Name: leave all entries as provided: Component: Controller: COMPONENTCONTROLLER Method: EXCUTE_ Press Continue.
5. Completing the Choice
When you have confirmed the last dialog box, the generation is triggered. Afterwards you now have the required methods
and contexts at your disposal for using them within your Web Dynpro component.
or if you want to call directly the use the call statement with destination

Error encountered while doing Migration from WLS 8.1 to WLS 10.0

Hello All ,
We are trying to do a WLS migrate(8.1 to 10.0) for a java/j2ee based application. We did not face any issues while compling application code (using jdk 1.5 & weblogic.jar of WLS 10.0) but while running the ant build script , we encountered an error while executing below part
Line: -----
1 <java classname="weblogic.appc" fork="true" maxmemory="${appc.java.maxmemory}" failonerror="true">
2 <classpath>
3 <pathelement path="${project.classpath}"/>
4 </classpath>
5
6 <jvmarg line="${appc.java.options} -Djava.io.tmpdir=${appc.tmp.dir}"/>
7
8 <arg line="-compiler ${appc.compiler} -output ${_appc.output}
9 -classpath ${_appc.classpath}
10 ${bmwslc.param.options}
11 ${appc.additional.options}
12 ${_appc.input}" />
13 </java>
Line: -----
Following is the error , which we encountered
Line: -----
# [java] Usage: java weblogic.appc [options] <ear, jar, war or rar file or directory>
# [java] where options include:
# [java] -help Print the standard usage message.
# [java] -version Print version information.
# [java] -output <file> Specifies an alternate output archive or
# [java] directory. If not set, output will be
# [java] placed in the source archive or directory.
# [java] -plan <file> Specifies an optional deployment plan.
# [java] -forceGeneration Force generation of EJB and JSP classes.
# [java] Without this flag the classes may not be
# [java] regenerated if it is determined to be
# [java] unnecessary.
# [java] -quiet Turns off output except for errors
# [java] -lineNumbers Add JSP line numbers to generated class
# [java] files to aid in debugging.
# [java] -library <file> Comma-separated list of libraries. Each
# [java] library may optionally set its name and
# [java] versions, if not already set in its
# [java] manifest, using the following syntax: <file>
# [java] [@name=<string>@libspecver=<version>
# [java] @libimplver=<version|string>]
# [java] -librarydir <dir> Registers all files in specified directory
# [java] as libraries.
# [java] -writeInferredDescriptors Write out the descriptors with inferred
# [java] information including annotations.
# [java] -keepgenerated Keep the generated .java files.
# [java] -verbose Compile with verbose output.
# [java] -classpath <path> Classpath to use.
# [java] -source <source> Source version.
# [java] -target <target> Target version.
# [java] -advanced Print advanced usage options.
# [java] <May 18, 2010 12:36:19 PM CEST> <Error> <J2EE> <BEA-160187> <weblogic.appc failed to compile your application. Recompile with the -verbose option for more details. Please see the error message(s) below.>
# [java] [J2EE:160128]ERROR: Incorrect appc command-line. Too many arguments were given. The command-line only takes a single argument, the source file, in addition to the supported options.
Line: -----
All the arguments looks correct to me while debugging . here is the summary of echo statements
${appc.additional.options} =""
${bmwslc.param.options} ="-forceGeneration"
${_appc.input}="test_ear-generic.ear"
I am dumb struck at this point
Please suggest any other thoughts , which you have in mind .
Thanks in advance !
Regards
Shobit

Probably too late for an answer but I try,
We are not able to build our J2EE 1.4 application with weblo 10, we have to build them with weblo 8 which contains the xdoclet. then we deploy it in WL10. then sometimes we have to fix some build constraints that WL10 doesn't allow anymore.

Using a counter on PCI-6023E DAQ card

Hi there,
I'm about to use a 6023 card to measure a periodic pulse signal. I need to count the number of the pulses. But...I've heard that the counters on my card are unusable in that case. Is that correct? Do I have to chage my card? Or can I do it with 6023E?
Thanks in advance;
Radek

Hi DAC,
The counter on your 6023E board is the DAQ-STC counter/timer. This counter fully supports counting the number of pulses. Depending on your application development environment, if you search the shipping examples you will find examples that perform this function.
This is so long as your digital pulses are 0-5 V or TTL compatible.
Other applications supported by your counter are:
Simple event counting
Gated-event counting
Single-period measurement
Single pulse-width measurement
Single pulse generation
Single triggered pulse generation
Retriggerable single pulse generation
Continuous pulse-train generation
Buffered event counting
Buffered period measurement
Buffered semi-period measurement
Buffered pulse-width measurement
Fre
quency measurement
Buffered frequency measurement
Finite pulse-train generation
Quadrature encoders
Hope that helps. Have a good day.
Ron
Application Engineering
National Instruments

Sequencing and Trigger on Oracle 9i lite database

We created a schema (TESTSCHEMA) on Oracle 8.1.7 Enterprise edition and have a created a trigger which will use the sequence object to generate primary key for the table (TEST_TABLE)
Sequence creation:
CREATE SEQUENCE TESTSCHEMA.TEST_TABLE_SEQUENCE START WITH 6000 INCREMENT BY 1 MINVALUE 6000 MAXVALUE 6999 NOCACHE NOCYCLE NOORDER ;
Trigger creation:
CREATE OR REPLACE TRIGGER TEST_TABLE INSERT BEFORE INSERT ON TEST_TABLE FOR EACH ROW
DECLARE
pkValue NUMBER;
BEGIN
pkValue := 0;
Select TEST_TABLE_SEQUENCE.NextVal into pkValue from dual;
:NEW.TEST_KEY := pkValue;
END TEST_TABLE_INSERT;
We have created a snapshot of the schema on mobile server, synchronized the data with the client (Win32 for testing purpose).
The trigger works fine on the server, but when I run the same query on the lite database with msql it gives me an error:
[POL-3221] null key in primary index
I was wondering if Sequence generation and Triggers are supported on Oracle 9i lite database ? Or am I missing out something ??
Any information/ help is appreaciated
Thanks
Neeraj

You can't use SAVEPOINT / ROLLBACK TO SAVEPOINT statements in the database trigger:
ORA-04092: cannot SET SAVEPOINT in a trigger
ORA-04092: cannot ROLLBACK in a trigger
I am not sure what you need exactly, but you can try this:
Simulating ROLLBACK TO SAVEPOINT Behavior in a Database Trigger
http://www.quest-pipelines.com/pipelines/plsql/tips02.htm#JUNE
Regards,
Zlatko Sirotic

Problems (?) with install CU4 on SCCM 2012 R2

Hi,
Today I have installed CU4 on my test SCCM enviroment (before I will install it on production). My test lab is:
1. One Primary Site server
2. One Secondary Site server
3. One server with Distribution Point role installed
First I have installed CU4 on Primary site server - without any issues.
Next I have done that same on Secondary site server - no problems also.
As final step I have use "Install Client" option with "Uninstall prevoius version". It has also was done with success.
After that I decided to check test infrastructure has been really updated to CU4. In distmgr.log, PkgXFer.log there was no errors. On ccmsetup.log there was info SCCm Client instalaltion has been done without errors also.
When I click RMB on distmgr.dll located on SMS\bin\x64 and choose Propoerties, there was info on "Detail" tab - file version 5.0.7958.1501. But when I do that same on smsexec.exe on "Details" tab there was file version 5.0.7958.1000 (that
situation is on all servers - PS, SS and DP as well..). It is normal? If not why it has been happened and how can I fix it?
I have next checked in SCCM console, on Asset & Complilance-->Devices all three servers in column "Client version" still has 5.00.7958.100 instead CU4... - I suppose it is not normal also...
Thank you for any suggestions and explanations.

Hi Bartas!
>here was file version 5.0.7958.1000
Not all files are modified by each CU. This is normal - smsexec.exe should still be at .1000 after applying CU4.
>"Client version" still has 5.00.7958.100 instead CU4... - I suppose it is not normal also...
This column will not be updated until the next Heartbeat discovery happens. You can force this by triggering the "Discovery Data Collection Cycle" client action on the device, waiting a few minutes, and then refreshing the record in the console.
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

String beginning ":OLD.DIAL_..." is too long. maximum size is 239 characte

@C:\Y\trigger.sql DIM_DIAL_DIGIT ctva_ra TRG_DIM_DIAL_DIGIT1
:OLD.DIAL_DIGIT_KEY,:OLD.BU_KEY,:OLD.NOP_ID_KEY,:OLD.SDCA_LOCATION_CODE,:OLD.TARGET_REGION_DESC,:OLD.TARGET_COUNTRY_CODE,:OLD.TARGET_COUNTRY_DESC,:OLD.LDCA_NAME,:OLD.SDCA_NAME,:OLD.LDCC_X_COORD,:OLD.LDCC_Y_COORD,:OLD.SDCC_X_COORD,:OLD.SDCC_Y_COORD,:OLD.POPULATION_DATE_TIME,:OLD.ISO_COUNTRY_CODE,:OLD.HOTLIST_IND,:OLD.BLACKLIST_IND,:OLD.UPDATE_DATE_TIME,:OLD.EVENT_TYPE_KEY,:OLD.PROVIDER_DESCRIPTION,:OLD.DM_IND,:OLD.DIAL_DIGIT_OPERATOR_TYPE,:OLD.CALL_DIRECTION_KEY,:OLD.DIAL_DIGIT_DESCRIPTION,:OLD.FORCE_RI_IND,:OLD.TEST_CALL_IND DIAL_DIGIT_KEY,BU_KEY,NOP_ID_KEY,SDCA_LOCATION_CODE,TARGET_REGION_DESC,TARGET_COUNTRY_CODE,TARGET_COUNTRY_DESC,LDCA_NAME,SDCA_NAME,LDCC_X_COORD,LDCC_Y_COORD,SDCC_X_COORD,SDCC_Y_COORD,POPULATION_DATE_TIME,ISO_COUNTRY_CODE,HOTLIST_IND,BLACKLIST_IND,UPDATE_DATE_TIME,EVENT_TYPE_KEY,PROVIDER_DESCRIPTION,DM_IND,DIAL_DIGIT_OPERATOR_TYPE,CALL_DIRECTION_KEY,DIAL_DIGIT_DESCRIPTION,FORCE_RI_IND,TEST_CALL_IND;
when i am running this script it return's string beginning ":OLD.DIAL_..." is too long. maximum size is 239 characters.
how will i overcome from this situation.
i am passing parameter with .sql file

Looks like you are trying to save the history data (with :OLD values).
If you are trying to generate a trigger at runtime, then you need a procedure which is able to loop through user_tab_columns for the given table and construct column strings for generation of triggers.
Then you can use EXECUTE IMMEDIATE to create the trigger.
Keep in mind that debugging such a procedure would be headache if you face any problems in creating the same.

Connecting to EJ bean in Sun App Server 8

I am working my way through the j2eetutorial14, and have successfully built the Converter app. However, I need to run the stand-alone client, connecting to the bean, in a server-independent way. So, as part of my exercise, I copied the client code in Eclipse, and made the following changes to the code:
from the original example:
Context initial = new InitialContext();
Context myEnv = (Context) initial.lookup("java:comp/env");
Object objref = myEnv.lookup("ejb/SimpleConverter");
ConverterHome home = (ConverterHome) PortableRemoteObject.narrow(objref, ConverterHome.class);to this:
Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
properties.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:3700");
Context initial = new InitialContext(properties);
Object objref = initial.lookup("ConverterBean");
ConverterHome home = (ConverterHome) PortableRemoteObject.narrow(objref, ConverterHome.class);Now I am getting this exception in the narrow() method:
java.lang.ClassCastException
     at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
     at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
     at ConverterClient.main(ConverterClient.java:27)When I run the client from the script:
appclient -client ConverterAppClient.jarit works as expected. I am obviously missing something in my Eclipse runtime environment, but the manual was of no help so far. (But j2ee.jar library from C:\Sun\AppServer\lib is in the classpath.)
If anyone successfully connected to the Sun App Server 8 EJB from a stand-alone client and can share their wisdom, I will appreciate it.
On a more general note, what are the pitfalls to watch for when writing, packaging and distributing an EJB app (bean and stand-alone client) in a server-independent way? Any pointers?
Thanks for any help.
Alex.

Did you have the EJB client JAR in your classpath? Yes, and I spent all day searching the Forums for the clues. I found the answer, and was going to post it here. The client JAR was missing the RMI stubs. The process of generating the stubs is quite cumbersome - at least, the one that I discovered. It involves deploying the EAR first, then going to the Admin Console and manually setting a number of options, then collecting the sought-for JAR from the Sun App Server's applications directory. The generated file will contain the stubs, and also the Home and Remote interface files, as well as the bean class (something that the client will never need). So, I may have to write a script to strip off the needless baggage from the client JAR.
I have been working with JBoss and its plugin for Eclipse for some time now, and grew spoiled by the ease of deployment there, including the fact that the JBoss/Eclipse combo took care of the RMI stubs and many other things that Sun's server exposes to the developer.
Anyway, here is my cookbook that I made as I was working through the process of generating the stubs:
====================================
Creating a stand-alone Client:
The stand-alone client need RMI stubs to communicate with the EJ bean on the server side. To create the stubs:
1. Start the Admin Console web page (Start > All Programs > Sun Microsystems > Application Server PE > Admin Console). In the left-hand frame select: Applications > Enterprise Applications.
2 In the right-hand frame, press Deploy button.
3 Select file to upoad (navigate to the application EAR). Press Next.
4. Set Application Name field (it should be preset), and check the Generate: RMIStubs checkbox. If this procedure was done before, check the Redeploy box to force generation of the file.
5. Press OK button.
The JAR file with stubs will be placed into C:\Sun\AppServer\domains\domain1\applications\j2ee-apps directory.
The stubs have format _name_Stub.class and _nameHome_Stub.class (e.g. for Converter app the files are ConverterStub.class and ConverterHomeStub.class). These files must be extracted and placed into the client's classpath. Alternatively, the entire JAR file can be made part of the client's classpath.
====================================
Thank you for the quick reply.
Alex.

R12.1.1: After cloning, unable to open any form .. APP-FND-01496

R12.1.1: After cloning, unable to open any form .. Getting the follownig error ..
Cannot complete applications login. You may have entered an invalid applications password, or there may have been a database connect error.
and ..
APP-FND-01496 ..

Hi Hussein,
How To solve The Login Errors : APP-FND-01931, APP-FND-01496, cause : Application Object Library was unable to access your ORACLE password ? [ID 787773.1]
Not appliable to my scenario.Unable To Launch Forms Receive Error App-fnd-01931 [ID 433554.1]
Done all following steps. No success...regenerate jar files - select YES when prompted to force generation of jar files.
recompile apps schema to check for invalid objects.
regenerate forms and pll's.
relink all applications programs - specifically f60webmx, although relinking all the applications executables is advisable.
recreate grants and synonyms.
recompile menus.
Clear Oracle jinitiator cache on client machine - typically c:\programs\oracle\jinit...\jcache .
Clear browser cache.
Bounce Oracle application services and re-test the issue.
Can Log Into Applications but Cannot Use Any Ad Tools [ID 391496.1]
I have already tried the recommended solution. No success.Is there any way to troubleshoot APP-FND-01496 and find out the root cause?
S. Sundar

Forcing Generation of Triggers

Similar Messages

Maybe you are looking for