Adding new element to BPEL for use in PL SQL type, has binding errors

Figured I might as well post this here since I haven't gotten a single reply in 3 days anywhere else :/
I have a BPEL service that calls a PL SQL procedure. I have added a new element to the BPEL called quote_cart_line.
All I had to the BPEL to accomplish this was edit 3 files -
Async_Invoke_Import_Model.xsd (Source)
<element name="orig_sys_line_ref" type="integer" minOccurs="1" nillable="true"/>
       <element name="quote_cart_line" minOccurs="1" nillable="true" type="integer"/>
      </sequence>
.....APPS_NI_MODEL_IMPORT_UTIL_IMPORT_SELECTIONS.xsd (Target)
<element name="ORIG_SYS_LINE_REF" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
         <element name="QUOTE_CART_LINE" type="decimal" db:type="NUMBER" minOccurs="0" nillable="true"/>
      </sequence>
.....Transform_NIE_Inputs.xsl (Transforming from Source to Target)
<ns1:orig_sys_line_ref>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:orig_sys_line_ref"/>
        </ns1:orig_sys_line_ref>
        <ns1:quote_cart_line>
          <xsl:value-of select="/ns1:Async_Invoke_Import_ModelProcessRequest/ns1:import_line/ns1:quote_cart_line"/>
        </ns1:quote_cart_line>
      </ns1:import_line>
.....I have done this to two other BPELs and they work fine. (1st BPEL calls the second BPEL passing this new element, which then passes it to this BPEL I am having trouble with, which then should be binding it to a PL SQL type)
So this BPEL calls a PL SQL procedure, binding the elements from the BPEL to a PL SQL type (ni_model_import_line). So I edited the PL SQL type to accept this new parameter:
orig_sys_header_ref       NUMBER,
       quote_cart_line           NUMBER,
       CONSTRUCTOR FUNCTION ni_model_import_line(p_part_number                IN VARCHAR2,
MEMBER PROCEDURE add_orig_sys_header_ref(p_org_sys_header_ref          IN NUMBER),
       MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER)
MEMBER PROCEDURE add_quote_cart_line(p_quote_cart_line                 IN NUMBER) IS
BEGIN
   quote_cart_line := p_quote_cart_line;
END add_quote_cart_line;
END;
.....I invoke all of this, and the new element gets populated in 3 different BPELs, including this one I explained here. But when it comes time to call the PL SQL I am now getting an error:
<fault>
-<bpelFault>
<faultType>0</faultType>
-<bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="summary">
<summary>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'nie_import_2' failed due to: Interaction processing error.
Error while processing the execution of the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API interaction.
An error occurred while processing the interaction for invoking the APPS.NI_MODEL_IMPORT_UTIL.IMPORT_SELECTIONS API. Cause: java.lang.NullPointerException
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
</part>
-<part name="detail">
<detail>null</detail>
</part>
-<part name="code">
<code>null</code>
</part>
</bindingFault>
</bpelFault>
</fault>This doesnt happen if I remove the references to this new element and try again, so it obviously is a problem with the element, but I have no idea what it is. It works fine when going from BPEL to BPEL, but as soon as the process tries to call the PL SQL procedure this happens. It is even more frustrating because I have done this exactly before adding another element, and it worked fine...
Any ideas or tips please?

Similar Messages

Is there an upgrade to Photoshop Elements 5.0 for use with Windows 8?

Is there an upgraded to Photoshop Elements 5.0 for use with Windows 8?

yes, photoshop elements 11 should be compatible with win 8 and there is an upgrade path here: http://www.adobe.com/products/photoshop-elements.html
(compatibility info: http://www.microsoft.com/en-us/windows/compatibility/en-US/CompatCenter/ProductViewerWithD efaultFilters?Architecture=X64&CurrentPage=0&TotalPages=-1&ShowCriteria=10%20Results%20Per %20Page&SortCriteria=Relevance&IsSearchWithinFilterAvailable=False&FilterByCompatibility=A LL&TextSearch=Photoshop&AbsolutePage=-1&LastRequested=13&LastSearchTerm=Photoshop )

Export of Elements 12 Project for use in Premiere Pro

Hello. Simply (or not so simply), I just want to know if I can export a Premiere Elements 12 Project for use in Premiere Pro CS6 or CC. I would like some form of verification such as a page in a manual or a link to a web page. Just getting the answer "Yes" will not do. Sorry but this has been very difficult to locate and am concerned it can't happen.
Thanks,
BK

"Adobe's target audience is just not likely to later need to edit a Project in a professional NLE."
Thanks Bill and I understand. However, given the current choices of NLE's today and many Professional Users "scrambling" to find replacements for FCP7 and "aging" Avid, I would think that the workflow I'm suggesting might be a cost effective and viable alternative that Adobe should consider very seriously. If it was never brought to their attention before, I'm mentioning it now!
If we can avoid the cost of putting PrPro into the hands of Preditors and leave the Pro Finishing to the real Pros, that would be very helpful not only financially but it would make learning and working with the software much easier for them using Elements.
So, I guess the only way to find out if this works, is to download the trial versions of each and have at it.
Unless someone out there already has both of the most current versions and is willing to try this?
Either way, I'll have to find out sooner or later because we are moving to Pro eventually.
Thanks again,
Bob K.

Senarious for using different internal table types

please give scenarios for using different internal table types?

Refer to the following.
Internal table types
This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the ABAP Dictionary.
Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.
TYPES <t> TYPE|LIKE <tabkind> OF <linetype> [WITH <key>]
[INITIAL SIZE <n>].
After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:
<tabkind> OF <linetype> [WITH <key>]
The type constructor defines the table type <tabkind>, the line type <linetype>, and the key <key> of the internal table <t>.
You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
Table type
You can specify the table type <tabkind> as follows:
Generic table types
INDEX TABLE
For creating a generic table type with index access.
ANY TABLE
For creating a fully-generic table type.
Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic type INDEX TABLE includes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
Fully-Specified Table Types
STANDARD TABLE or TABLE
For creating standard tables.
SORTED TABLE
For creating sorted tables.
HASHED TABLE
For creating hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
Line type
For the line type <linetype>, you can specify:
Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the ABAP Dictionary. If you specify any of the generic elementary types C, N, P, or X, any attributes that you fail to specify (field length, number of decimal places) are automatically filled with the default values. You cannot specify any other generic types.
Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and structures in the ABAP Dictionary (for compatibility reasons).
All of the lines in the internal table have the fully-specified technical attributes of the specified data type.
Key
You can specify the key <key> of an internal table as follows:
[UNIQUE|NON-UNIQUE] KEY <col1> ... <col n>
In tables with a structured line type, all of the components <coli> belong to the key as long as they are not internal tables or references, and do not contain internal tables or references. Key fields can be nested structures. The substructures are expanded component by component when you access the table using the key. The system follows the sequence of the key fields.
[UNIQUE|NON-UNIQUE] KEY TABLE LINE
If a table has an elementary line type (C, D, F, I, N, P, T, X), you can define the entire line as the key. If you try this for a table whose line type is itself a table, a syntax error occurs. If a table has a structured line type, it is possible to specify the entire line as the key. However, you should remember that this is often not suitable.
[UNIQUE|NON-UNIQUE] DEFAULT KEY
This declares the fields of the default key as the key fields. If the table has a structured line type, the default key contains all non-numeric columns of the internal table that are not and do not contain references or internal tables. If the table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
Specifying a key is optional. If you do not specify a key, the system defines a table type with an arbitrary key. You can only use this to define the types of field symbols and the interface parameters of procedures . For exceptions, refer to Special Features of Standard Tables.
The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
You must always specify the UNIQUE option when you create a hashed table.
Initial Memory Requirement
You can specify the initial amount of main memory assigned to an internal table object when you define the data type using the following addition:
INITIAL SIZE <n>
This size does not belong to the data type of the internal table, and does not affect the type check. You can use the above addition to reserve memory space for <n> table lines when you declare the table object.
When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each are then allocated.
You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The space occupied, depending on the line width, is 16 <= <n> <= 100.
It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the length of the line. If you specify a larger value of <n>, the system calculates a new value so that n times the line width is around 12KB.
Examples
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
The program defines a table type ITAB. It is a sorted table, with line type of the structure LINE and a unique key of the component COLUMN1.
TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
TYPES: BEGIN OF DEEPLINE,
FIELD TYPE C,
TABLE1 TYPE VECTOR,
TABLE2 TYPE ITAB,
END OF DEEPLINE.
TYPES DEEPTABLE TYPE STANDARD TABLE OF DEEPLINE
WITH DEFAULT KEY.
The program defines a table type VECTOR with type hashed table, the elementary line type I and a unique key of the entire table line. The second table type is the same as in the previous example. The structure DEEPLINE contains the internal table as a component. The table type DEEPTABLE has the line type DEEPLINE. Therefore, the elements of this internal table are themselves internal tables. The key is the default key - in this case the column FIELD. The key is non-unique, since the table is a standard table.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm

Adding new elements to a Master Page and sharing them to existing pages

I need to include new navigation elements on the master page
and I want it to show up on pages I've already created. I've added
the new elements on a layer of their own which is part of the
master page, but the Share Layer to Pages... option is dimmed.

jcbluesman wrote:
> I'm using CS4, Jim, and here's a link to the .png
> (
http://idisk.mac.com/jconstant-Public/deimos.png
>
> The 3 tabs in the upper right on the master page are the
ones I'm trying to
> share across the existing pages. I created them in PS
(also CS4), then imported
> the .psd into this FW document, if that makes any
difference.
>
> Thanks,
> Jim
>
OK there are two related as I see it.
Each of your pages consists of a solid, opaque bitmap for a
main image.
Master Pages, by default, are at the bottom of the layer
stack. Your
tabs ARE present, you just can't see them because they are
covered up by
the bitmap.
Assuming you don't have those page images as multi-object
elements,
where you can edit the blue backgrounds, there are still two
things you
can do, both of which are pretty easy.
Go into each page and temporarily reduce the opacity of Layer
1.
Use the marquee tool to draw a selection around the area of
the tabs.
Delete the selection.
Return the lay back to full opacity.
OR
Try dragging the Master page to the top of the layer stack in
each page.
Hide or delete the Master page background.
This option is a little trickier, but I was able to do it.
Wait for the
black bar to appear before you release the mouse. You may
need to try
this a few times before it works.
HTH
Jim Babbage - .:Community MX:. & .:Adobe Community
Expert:.
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
.:Adobe Community Expert for Fireworks:.
Adobe Community Expert
http://tinyurl.com/2a7dyp
.:Author:.
Lynda.com -
http://movielibrary.lynda.com/authors/author/?aid=188
Peachpit Press -
http://www.peachpit.com/authors/bio.aspx?a=d98ed798-5ef0-45a8-a70d-4b35fa14c9a4
Layers Magazine -
http://www.layersmagazine.com/author/jim-babbage

Adding new element block before the original nodes

I want to form a new xml like this:
<xml>
<form id="name1"> // this is
</form> // new element i'll add
<form id="_name1"> // this is
</form> // original element
<form id="name2"> // this is
</form> // new element i'll add
<form id="_name2"> // this is
</form> // original element
</xml>
how to insert new element parts into xml file by using Jdom?
Thanks
jj

Sorry for my format
I added i.previous();
                                        i.add(newFormElement);
                                        i.next();still not work properly.
How can i do?? pls see my code again!
     public void modifyvxml(Document doc){
               Element root = doc.getRootElement();
               java.util.List forms = root.getChildren();
               if(forms.size()>0)
                    for(int formloop=0; formloop < forms.size() ; formloop++)
                         List newFormList = new java.util.LinkedList();
                         Element form = (Element)forms.get(forms.size());
                         String form_id = form.getAttributeValue("id");
                         System.out.print ("Form_id is "+form_id+"\n");
               ListIterator i = forms.listIterator();
               while (i.hasNext()) {
                    Element form = (Element) i.next();
                         String form_id = form.getAttributeValue("id");
                         if(form_id != null){
                                        int j = 0;
                                        StringBuffer sb_form = new StringBuffer(form_id);
                                        sb_form.insert(0, '_');
                                        form_id = sb_form.toString();
                                        form.setAttribute("id", form_id);
//==================add new forms
                                        Element newFormElement = new Element("form");
                                        Element subdialog = new Element("subdialog");
                                        int index = forms.indexOf(newFormElement);
                                        newFormElement.setAttribute("id", form_id);
                                        newFormElement.addContent(subdialog);
                                        subdialog.setAttribute("src", "call.jsp");
                                        i.previous();
                                        i.add(newFormElement);
                                        i.next();
//                                        newFormList.add(formloop,newFormElement);
//                                        newFormList.add(formloop,forms);
                    System.out.print ("new form_id is "+form_id+"\n");
//=====================
                    try{
                    XMLOutputter out = new XMLOutputter();
                    File myXML = new File("testvxml.xml");
                    out.output(doc,new FileOutputStream(myXML));
                    }catch (IOException e) {
                    e.getMessage();
}Thanks

NewElementInHierarchy() - Adding New Elements, progressively takes longer when adding multiple siblings

With my ESTK script, users select model numbers from a list and then the script inserts an element with a model number entered into an attribute, one element for each model selected.
When adding a large number of elements, each additional sibling element takes a little longer to add then the previous element. Adding 250 elements can take upwards of 3-1/2 minutes or more. While adding 20, 50, or 75 elements happens quickly, without any noticeable duration. It’s somewhere above 110 is where it starts to be noticeable.
I even used $.hiresTimer and wrote the value to the console for each time a model was added. Since the timer is reset back to zero (0) each time it's called, it was easier to notice that the amount it incremented from one element to the next got progressively larger.
Any thoughts as to why it’s taking so long or thoughts on what I could do to speed it up?
The structure looks like this:
<PartModels>
      <NoteText>Text</NoteText>
      <Model ModelNumber=”ABC01”/>
      <Model ModelNumber=”ABC02”/>
      <Model ModelNumber=”DEF03”/>
      <Model ModelNumber=”DEF04”/>
      <Model ModelNumber=”XYZ01-A”/>
      <Model ModelNumber=”XYZ*B”/>
      <Model ModelNumber=”XYZ500”/>
</PartModels>
The script is somewhat straight forward: cycle through an array of the model numbers selected, add a new element for each model number and set it's attribute value to the model number. This is the short version:
Function InsertModelElements (modelsToIns, insElemLoc, GVdoc) {
     var newEleId;
     var newElemLoc = insElemLoc;
     var elemDef = GVdoc.GetNamedElementDef(“Model”);
     for(var i = 0; i < modelsToIns.length; i++){ // modelsToIns is the array of models selected
          newEleId = elemDef.NewElementInHierarchy(newElemLoc); //ElementLoc based on NoteText first, last, or not present
          SetAttribute(newEleId, "ModelNumber", null, modelsToIns[i]); //more robust function to set attribute
          /*Which also works for setting attribute*/
          //var vattributes = newEleId.GetAttributes();
          //vattributes[0].values[0] = modelsToIns[i];
          //newEleId.Attributes = vattributes;
          /*At one point I tried using a new element location from the last inserted element, no change*/
          //var newElemRange = setElementSelection(GV_doc, EleId); //function that returns range
          //newElemLoc = newNewElemRange.end;
Any help is appreciated.
Sincerely,
Trent

Thanks Russ,
I seriously considered trying copy/paste and started to modify the code to do so. But I couldn't let it go, the answer had to be right there in front of me, just it's been too long since I've worked with this stuff, I'm not able to see it. Then it dawned on me what is happening.
In an earlier test, I placed a timer on each action that is looped through. For example, I start with an container element that has 200 children elements, each with a specific/unique model number attribute. All 200 existing elements are deleted and then replaced with 250 new elements with a different value for the model number attribute. The timer was placed after the Element.Delete() method and ElementDef.NewElementInHierarchy() method. What I noticed with the timer is that each element deleted was deleted faster than the previous element (so it progressively took less and less time to delete an element). And of course the opposite was noticed for inserting elements, each element inserted took longer than the previous element inserted.
These elements can be inserted in two areas of the structure, one of the areas has fewer format rules that impact the formatting and is actually a little quicker. This led me to the cause being the EDD format rules. The area that takes longer has quite a few extensive format rules that apply. Every time an element is inserted or deleted, FrameMaker runs through those rules to format the content of the elements. Since the rules apply to parent, first, last, next, previous, etc., FrameMaker has to apply format rules to all the elements in the structure that the rules apply to (which are extremely complex because of the various elements, attribute values, and combinations that can be inserted).
Removing or thinning down the FormatRules in the EDD, it does get quicker. But each of the FormatRules are needed. So using app.ApplyFormatRules = false; right before the elements are deleted and inserted works great. But the key is to set ApplyFormatRules back to true before deleting the last element to be deleted and before inserting the last element to be inserted, so it will cycle through all the format rules of the EDD for all the elements in the hierarchy those format rules apply to. Setting ApplyFormatRules to true and assigning the ElementDef to the last element also works [EleId.ElementDef = GV_doc.GetNamedElementDef(insElemType);], but only before any other functions are performed or different elements are added.
doc.Reformat() isn't going to reformat the content correctly after the fact because the element was created without the format rules, so it just reformats the content of the elements without the format rules.
The FDK version that was created 10 years ago had the same problem of running slow when a large number of elements were being inserted, but was still an improvement over having to manually insert each element and type in the attribute value, so it was lived with.
It's now working amazingly fast. I hope my explanation of what I think is happening, including the cause/solution, is understandable.
Sincerely,
Trent Schwartz

I cannot see my new WD My Passport for Mac hardrive in finder, it has USB 3, compatible withUSB 2. I can see it in disk utility

My new WD My Passport for mac,1 Tb harddrive in finder. it's there initially then disapears, I can see it in disk utilities and in the systrm report, so I think it is moounting, but difficult to access and to ejet when not visible in the finder sidebar. This has a USB 3 connection, whic i states is also compatible with USB 2

Check the format of the drive when in disk utility. It should be
Mac OS Extended (Journaled)
A powererd external usb hub can help when the computer's usb port is marginal.

Is there a way to see what font was used originally, after the type has been converted to outlines?

Hi all, I would really like to know if there is any way to find out what font was used originally in an Illustrator document, after the type has been converted to outlines? The reason for this is I need to update some wording in a couple of old logos I had made and I have NO idea what font I had used...for the life of me I just cannot remember. Because this was so urgent for one of my projects I had to do a search online via "WhatTheFont" to see what font it could be (which I then didn't seem to have in my library!), and repurchase it. I am 99% sure I HAVE the font - or something VERY close - but under a different name.
Normally I keep a much better record of fonts used but there have been times occasionally in the past when I have done something in a hurry and changed the type to outlines without keeping the original, or keeping detailed notes at least. The fact that I did NOT keep notes on a few projects I have done in the past has made me want to kick myself because now I need to revisit one of those again..grrr:)
Can anyone offer any advice? I appreciate your help as always:)
best,
Christine

Christine,
You can also ask in the Typography forum,
http://forums.adobe.com/community/design_development/typography?view=discussions&start=0
The guy running whatfontis is a regular poster there.
And apart from
http://www.whatfontis.com/
there are
http://www.identifont.com/
http://new.myfonts.com/WhatTheFont/
and especially for script,
http://www.bowfinprintworks.com/ScriptIDGuide.html

Use of PL/SQL %TYPE and HS

I have been unable to get a PL/SQL package specification to compile that uses %TYPE against a table that is referenced via a HS link and physically resides in MSSQL 7.
The documentation I looked at (Oracle Transparent Gateway A82868-01 for 8.1.6 and A88789-01 for 9.0.1) does not specifically state if this functionality is supported or not. My database level is 8.1.7.1.5.
I assume that if this is supported then Oracle does some translation of data types at compile time. If it is not suppported then I can remove the use of %TYPE and type the variables using the Raw data type.
My line of code in the package spec is:
PROCEDURE RFQ_HDR_OUT
( i_rfqnum IN "rfq"."rfqnum"%TYPE);
I have also tried:
PROCEDURE RFQ_HDR_OUT
( i_rfqnum IN rfq.rfqnum%TYPE);
PROCEDURE RFQ_HDR_OUT
( i_rfqnum IN "dbo"."rfq"."rfqnum"%TYPE);
PROCEDURE RFQ_HDR_OUT
( i_rfqnum IN rfq."rfqnum"%TYPE);
The error I get is:
(1): PLS-00201: identifier 'rfq.rfqnum' must be declared
The rfq reference is actually a Oracle VIEW built on a SELECT * FROM table@HSODBC. I can successfully select data from this table using SQL*Plus.
I am also able to reference this table in my package BODY without a problem.
Any insight much appreciated.
Regards, Charles.

The compilation of the package does not create any trace output.
My trace settings in hs\admin\inithsodbc.ora are:
# HS init parameters
HS_FDS_CONNECT_INFO=mssql
HS_FDS_TRACE_LEVEL = 4
HS_FDS_TRACE_FILE_NAME = hsodbc.trc
I can however successfully run a SELECT against the same VIEW that I am trying to use for %TYPE in my package. This SELECT renders the following trace:
TUESDAY MAY 14 2002 15:33:12.031
(0) hoagprd(2); Entered.
(0) [Generic Connectivity Using ODBC] version: 2.0.4.0.0010
(0) connect string is:
(0) YEAR2000_POLICY=-1;CTL_DEBUG=T;CONSUMER_API=1;SESSION_BEHAVIOR_FLAGS=4;PARSER_-
(0) DEPTH=2000;EXEC_FLAGS = 131080;defTdpName=hsodbc;binding=(hsodbc,ODBC,"mssql");
(0) ORACLE GENERIC GATEWAY Log File Started at 14-May-02 15:33:12
(0) Class version: 65
(0) hoagprd(2); Exited with retcode = 0.
(0) hoainit(3); Entered.
(0) hoainit(3); Exited with retcode = 0.
(0) hoalgon(7); Entered. name = maximo.
(0) Created new ODBC connection (27792120)
(0) hoalgon(7); Exited with retcode = 0.
(0) hoaulcp(4); Entered.
(0) hoaulcp(4); Exited with retcode = 0.
(0) hoauldt(5); Entered.
(0) hoauldt(5); Exited with retcode = 0.
(0) hoabegn(9); Entered. formatID = 306206, hoagttid =BATT.d2ea68f8.3.1.11,
(0) hoagtbid = , tflag = 0, initial = 1
(0) hoabegn(9); Exited with retcode = 0.
(0) hoapars(15); Entered. stmtType = 0, id = 1.
(0) nvOUT (P:\Src\QP\QP_SQTXT.C 55): SELECT * FROM "RFQ"
(0) odbc_rec: select * from "RFQ"
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 929):
(0) SELECT "T0000"."buyercompany" AS c00039, "T0000"."printdate" AS c00038, "T0000"."ldkey" AS c00037, "T0000"."rfq10" AS c00036, "T0000"."rfq9" AS c00035, "T0000"."rfq8" AS c00034, "T0000"."rfq7" AS c00033, "T0000"."rfq6" AS c00032, "T0000"."rfq5" AS c00031, "T0000"."rfq4" AS c00030, "T0000"."rfq3" AS c00029, "T0000"."rfq2" AS c00028, "T0000"."rfq1" AS c00027, "T0000"."historyflag" AS c00026, "T0000"."priority" AS c00025, "T0000"."changedate" AS c00024, "T0000"."changeby" AS c00023, "T0000"."paymentterms" AS c00022, "T0000"."shipvia" AS c00021, "T0000"."freightterms" AS c00020, "T0000"."fob" AS c00019, "T0000"."replytoattn" AS c00018, "T0000"."replyto" AS c00017, "T0000"."billtoattn" AS c00016, "T0000"."billto" AS c00015, "T0000"."shiptoattn" AS c00014, "T0000"."shipto" AS c00013, "T0000"."requestedby" AS c00012, "T0000"."requireddate" AS c00011, "T0000"."rfqtype" AS c00010, "T0000"."purchaseagent" AS c0009, "T0000"."closeondate" AS c0008, "T0000"."replydate" AS c0007, "T0000"."enterby" AS c0006, "T0000"."enterdate" AS c0005, "T0000"."statusdate" AS c0004, "T0000"."status" AS c0003, "T0000"."description" AS c0002, "T0000"."rfqnum" AS c0001, "T0000"."rowstamp" AS c0000 FROM "RFQ" T0000
(0) nvOUT (P:\Src\QP\QPT2SEXE.C 932):
(0) <<<<<<<<<<<<<<<<<<< Execution Strategy Begin <<<<<<<<<<<<<<<<<<<<<<<<<<<<
(0) Original SQL:
(0) SELECT * FROM "RFQ"
(0)
(0)
(0) Accessing Database "hsodbc" with SQL:
(0) SELECT "T0000"."buyercompany" AS c00039, "T0000"."printdate" AS c00038, "T0000"."ldkey" AS c00037, "T0000"."rfq10" AS c00036, "T0000"."rfq9" AS c00035, "T0000"."rfq8" AS c00034, "T0000"."rfq7" AS c00033, "T0000"."rfq6" AS c00032, "T0000"."rfq5" AS c00031, "T0000"."rfq4" AS c00030, "T0000"."rfq3" AS c00029, "T0000"."rfq2" AS c00028, "T0000"."rfq1" AS c00027, "T0000"."historyflag" AS c00026, "T0000"."priority" AS c00025, "T0000"."changedate" AS c00024, "T0000"."changeby" AS c00023, "T0000"."paymentterms" AS c00022, "T0000"."shipvia" AS c00021, "T0000"."freightterms" AS c00020, "T0000"."fob" AS c00019, "T0000"."replytoattn" AS c00018, "T0000"."replyto" AS c00017, "T0000"."billtoattn" AS c00016, "T0000"."billto" AS c00015, "T0000"."shiptoattn" AS c00014, "T0000"."shipto" AS c00013, "T0000"."requestedby" AS c00012, "T0000"."requireddate" AS c00011, "T0000"."rfqtype" AS c00010, "T0000"."purchaseagent" AS c0009, "T0000"."closeondate" AS c0008, "T0000"."replydate" AS c0007, "T0000"."enterby" AS c0006, "T0000"."enterdate" AS c0005, "T0000"."statusdate" AS c0004, "T0000"."status" AS c0003, "T0000"."description" AS c0002, "T0000"."rfqnum" AS c0001, "T0000"."rowstamp" AS c0000 FROM "RFQ" T0000
(0)
(0)
Execution Strategy End >>>>>>>>>>>>>>>>>>>>>>>>>>>>(0) hoapars(15); Exited with retcode = 0.
(0) hoaopen(19); Entered. id = 1.
(0) hoaopen(19); Exited with retcode = 0.
(0) hoadscr(16); Entered. id = 1.
(0) hoastmt(195); Array fetch size is: 1.
(0) ------ hoadscr() -------:
(0) hoadamsz: 40, hoadasiz: 40, hoadambr: 1, hoadabrc: 1
(0) row 0 - hoadambl: 0, hoadadty: 0, hoadaprc: 0, hoadacst: 0
(0) row 0 - hoadascl: 0, hoadanul: 0, hoadanml: 8, hoadanam: rowstamp, hoadabfl:
(0) 0, hoadamod: 0
(0) row 1 - hoadambl: 8, hoadadty: 108, hoadaprc: 8, hoadacst: 0
(0) row 1 - hoadascl: 0, hoadanul: 0, hoadanml: 6, hoadanam: rfqnum, hoadabfl: 8,
(0) hoadamod: 0
(0) row 2 - hoadambl: 50, hoadadty: 108, hoadaprc: 50, hoadacst: 0
(0) row 2 - hoadascl: 0, hoadanul: 1, hoadanml: 11, hoadanam: description,
(0) hoadabfl: 50, hoadamod: 0
(0) row 3 - hoadambl: 6, hoadadty: 108, hoadaprc: 6, hoadacst: 0
(0) row 3 - hoadascl: 0, hoadanul: 0, hoadanml: 6, hoadanam: status, hoadabfl: 6,
(0) hoadamod: 0
(0) row 4 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 4 - hoadascl: 0, hoadanul: 0, hoadanml: 10, hoadanam: statusdate,
(0) hoadabfl: 7, hoadamod: 0
(0) row 5 - hoadambl: 7, hoadadty: 167, hoadaprc: 0, hoadacst: 0
(0) row 5 - hoadascl: 0, hoadanul: 1, hoadanml: 9, hoadanam: enterdate, hoadabfl:
(0) apiutil; row 39 - cbDataOffset: 839, dwBinding: 1, width: 18, scale: 0
(0) hoaftch(21); Exited with retcode = 1403, hoadabrc = 0.
(0) hoaclse(22); Entered. id = 1.
(0) hoaclse(22); Exited with retcode = 0.
(0) hoadafr(23); Entered. id = 1.
(0) hoadafr(23); Exited with retcode = 0.
(0) hoacomm(11); Entered. keepinfo = FALSE, tflag = 1.
(0) hoacomm(11); Exited with retcode = 0.
Regards, Charles.

Adding new field at leasing contract using EEWB and using it for pricing

Using the Easy enhancement workbench, I have created a new tab containing a new field at the item level of contract. Then in SPRO, in the field catalog, I added a new entry using the same field name and data element name. Created a new condition table with this new field. created access sequence and assigned it to a condition type.
I tried to maintain condition record for the condition type but initially it was showing some error for which I had to implement a new method for the BAdi /SAPCND/ROLLNAME.
Now. condition record is also maintained successfully.
But, the problem is that the value is not reflected at the contract.
Somehow, the condition record is not being picked up.
Please suggest some solution.
Regards,
Anindita RoyChowdhury.

Hi Anindita,
Stpes mentioned in your questions are fine.
You have created new Screen @ item level in Order txn, right?
Did u checked value passed to the method of BAdI ?
As per my knowledge, pricing call must have happened before you fill the Zfield which u added in new screen. Hence no value in field and no effect on pricing.
Regards,
Deven

ReGeneration of a task form after adding new element in the payload

Hello,
I have a question concerning the re-Generation of a task form
In a first step we have made a BPM Process with a Human task. We have generated the task form.
In a second step we have changed the payload definition in the Human Task (i.e adding an attribut).
How can we re-generate the existing ADF form or modify the Data Control wihtout creating a new ADF project ?
Thanks,
Grégoire.

When you use the auto generate task form feature, it creates a new project for the form. You can also use the manual generate function to add a form to an existing project. But, you can't replace an existing form with the new one this way.
You could update an existing form to access the new data element (theoretically - though you'd have to do a bit of manual puttering around) but if you have not customized the form, there is no benefit in doing it this way.
Heidi.

Cancelling a line and and adding new lines to existing PO using API

Hi,
Can any one please help me know how I can cancel a line and insert new lines into a existing PO using any API.
Many Thanks,
Srinivas.

VanessaC_VZW wrote:
However, if you do not want a contract on the new lines, (since you will have your own equipment), the activation fee will be $35.00 per line. If you agree to a 2-year contract for the share lines, the activation fees will be $25.00 per line.
You can add the new lines by calling our Telesales Department at 800-256-4646.
Thank you,
Really?! I didn't know that made a difference...I thought secondary lines were $25 - well, ya learn something new every day!
And a side note - we added a line for my 75+ yr old mother with one of our old flip phones and CS was extremely kind in waiving the activation fee (I could have sworn it was $25 charged and credited on the bill), PLUS they boxed up the flip phone after activating it (with an out of state number to boot) and shipped it to my Mom, all at no additional cost to me. I'm not saying that will be everyone's experience, and I was amazed the service rep offered to ship it for me - but I smiled and said "THANK YOU!" and accepted it!

Adding new Condition Rule attribute for "ICRULE-Intent Driven Interaction"

Hi Experts,
I want to add a Z attribute for context "ICRULE- Intent Driven Interaction".
Under SPRO path Customer Relationship Management->E-Mail Response Management System->Define Repository
I define new Condition Attribute Z_BP_NUMBER with is the copy of BP_NUMBER Attribute.
1. if i define a Rule to trigger the Alert with Condition Attribute BP_NUMBER is XYZ. then Alert gets Triggered.
2. if i define a Rule to trigger the Alert with Condition Attribute Z_BP_NUMBER is XYZ. then Alert is not Triggered.
After defining Condition Attribute Z_BP_NUMBER at Define Repository (spro) do i need to include at any other placel?
Please help me with your valuable input.
Thanks and Regards,
Vimal

Hello Vimal,
Yes, you also need to create your own data collector class and fact gathering service to use your new attribute! If you have a subscription to CRM Expert, you can read this detailed article that I co-wrote on using your own custom attributes: http://www.crmexpertonline.com/article.cfm?id=5475.
Regards,
John

Adding new lines on outbound delivery using decentral warehouse

Hi
I have a decentralized warehouse that reports back to SAP for our outbound deliveries.
When the systems responds it can add an extra line, if a item can not be delivered. but it is possible to add an similar item, but with a different item number.
Can I add new line items to a delivery using SHP_OBDLV_CHANGE or any other idoc, or do I need to use a RFC/BAPI.
Regards
Daniel

FM or BAPI to add line item to SD Delivery

Adding new element to BPEL for use in PL SQL type, has binding errors

Similar Messages

Maybe you are looking for