Inbound Condition in the PO

Hi Gurus,
Following is the scenario;
POS creates a Purchase Order
Inbound occurs to SAP through IDOC .PO created in SAP.
If we maintain a condition type in the pricing procedure,and if the condition record is
maintained,the condition type is getting populated in all the inbound Purchase orders.
Now say,POS has entered a manual condition type only for selected Purchase orders.
We want to get the condition type populated in the inbound Purchase order to SAP as well.
In a nutshell,our requirement is only when POS enters a condition type in the Purchase orders,
the same has to be populated in the inbound Purchase orders to SAP.
Points for sure
Best Regards

Hi,
Manually active indicator is checked already in the calculation schema.
This will be fine when the PO is created and changed in SAP itself .
But our requirement is when POS creates a PO and entering a condition type,
the same should get populated in SAP.
How to capture the same,FYI, we are using IDOC type "PORDCR102".
Best Regards

Similar Messages

If..then..else statement in SQL with 'generalized' conditions in the if sta

it is possible to write something approaching an if..then..else statement in SQL with 'generalized' conditions in the if statement.
Attached is the query for the payment register, in which I've written a series of decode statements, one for each possible value of the payment code. The query works OK - however, its specific and as the number of paycodes expand (and they do), the report won't pick up the new paycode until the code is changed. More importantly, the report won't be correct until someone 'discovers' that a paycode is missing, which might take months.
If I were writing the equivalent of this series of decode statements in Focus, it would be something like this:
DEFINE.......
PAYMED/D12.2 = IF PAYMENT_CD LE 18
               THEN PAYMENT_AMT
               ELSE 0 ;
PAYIND/D12.2 = IF PAYMENT_CD GE 19 AND PAYMENT_CD LE 49
               THEN PAYMENT_AMT
               ELSE 0 ;
PAYEXP/D12.2 = IF PAYMENT_CD GE 70
               THEN PAYMENT_AMT
               ELSE 0 ;
PAYREC/D12.2 = IF PAYMENT_CD GE 50 AND PAYMENT_CD LE 69
               THEN PAYMENT_AMT
               ELSE 0;
END
IN SQL/PLUS:
SELECT ACCOUNT_NAME,
LOCATION_1,
CLMNT_LAST_NAME,
CLAIM_NBR,
DATE_OF_INJURY,
DATE_CHECK_REGISTER,
PAYEE_NAME_1,
PAYMENT_CD,
SERV_OFC,
CPO_CHECK_NBR,
PAYMENT_FORM,
DECODE(PAYMENT_CD, 20, PAYMENT_AMT, 21, PAYMENT_AMT,
22, PAYMENT_AMT, 23, PAYMENT_AMT, 25, PAYMENT_AMT,
26, PAYMENT_AMT, 27, PAYMENT_AMT, 28, PAYMENT_AMT,
29, PAYMENT_AMT, 30, PAYMENT_AMT, 31, PAYMENT_AMT,
32, PAYMENT_AMT, 33, PAYMENT_AMT, 34, PAYMENT_AMT,
35, PAYMENT_AMT, 36, PAYMENT_AMT, 37, PAYMENT_AMT,
39, PAYMENT_AMT, 40, PAYMENT_AMT, 41, PAYMENT_AMT,
42, PAYMENT_AMT, 43, PAYMENT_AMT, 44, PAYMENT_AMT,
45, PAYMENT_AMT, 46, PAYMENT_AMT, 47, PAYMENT_AMT,
48, PAYMENT_AMT, 49, PAYMENT_AMT, NULL) INDEMNITY,
DECODE(PAYMENT_CD, 0, PAYMENT_AMT, 1, PAYMENT_AMT,
2, PAYMENT_AMT, 3, PAYMENT_AMT, 4, PAYMENT_AMT,
5, PAYMENT_AMT, 6, PAYMENT_AMT, 7, PAYMENT_AMT,
8, PAYMENT_AMT, 9, PAYMENT_AMT, 10, PAYMENT_AMT,
11, PAYMENT_AMT, 12, PAYMENT_AMT, 13, PAYMENT_AMT,
14, PAYMENT_AMT, 15, PAYMENT_AMT, 18, PAYMENT_AMT,
17, PAYMENT_AMT, NULL) MEDICAL,
DECODE(PAYMENT_CD, 70, PAYMENT_AMT, 71, PAYMENT_AMT,
72, PAYMENT_AMT, 73, PAYMENT_AMT, 74, PAYMENT_AMT,
75, PAYMENT_AMT, 76, PAYMENT_AMT, 77, PAYMENT_AMT,
78, PAYMENT_AMT, 79, PAYMENT_AMT, 80, PAYMENT_AMT,
81, PAYMENT_AMT, 82, PAYMENT_AMT, 83, PAYMENT_AMT,
84, PAYMENT_AMT, 85, PAYMENT_AMT, 86, PAYMENT_AMT,
87, PAYMENT_AMT, 88, PAYMENT_AMT, 89, PAYMENT_AMT,
90, PAYMENT_AMT, NULL) EXPENSES,
DECODE(PAYMENT_CD, 50, PAYMENT_AMT, 51, PAYMENT_AMT,
52, PAYMENT_AMT, 53, PAYMENT_AMT, 54, PAYMENT_AMT,
55, PAYMENT_AMT, 56, PAYMENT_AMT, 57, PAYMENT_AMT,
58, PAYMENT_AMT, NULL) RECOVERIES,
DECODE(PAYMENT_FORM, 'N', PAYMENT_AMT, NULL) NONCASH,
DATE_FROM_SERVICE,
DATE_THRU_SERVICE
FROM &INPUT_TABLES
WHERE &SECURITYCOND
DATE_OF_PAYMENT BETWEEN :START_DATE AND :END_DATE
ORDER BY LOCATION_1, CPO_CHECK_NBR
As you can see, this is both much easier to write and covers the possibility of expansion of paycodes (expansions always fit in these defined ranges).
My question is, then, is it possible to write something like this in SQL and, if so, could you give me some sample code? (I'm one of those people who learn best from looking at the code as opposed to a set of instructions)

Here is one way you could do it.
Create a table that has columns like:
Payment_code varchar2(2),
Effective_Date Date,
Payment_type varchar2(20),
Expiration_Date Date)
Payment type for example could be
I- indemnity
M- medical
R- recovery
E- expenses
Let the table name for example be PAYMENT_CODE.
The select query would look like
SELECT ACCOUNT_NAME,
LOCATION_1,
CLMNT_LAST_NAME,
CLAIM_NBR,
DATE_OF_INJURY,
DATE_CHECK_REGISTER,
PAYEE_NAME_1,
PAYMENT_CD,
SERV_OFC,
CPO_CHECK_NBR,
PAYMENT_FORM,
DECODE(p.payment_type,'E',PAYMENT_AMOUNT,0) expenses,
DECODE(p.payment_type,'I',PAYMENT_AMOUNT,0) indemnity,
DECODE(p.payment_type,'M',PAYMENT_AMOUNT,0) Medical,
DECODE(p.payment_type,'R',PAYMENT_AMOUNT,0) recoveries,
DECODE(PAYMENT_FORM, 'N', PAYMENT_AMT, NULL) NONCASH
FROM &INPUT_TABLES,
PAYMENT_CODE P
WHERE P.PAYMENT_CODE = SOMEINPUT_TABLE.PAYMENT_CODE
and other conditions
The idea is to group all the payment codes into a few groups to reduce the clutter. If there is ever a change to the payment code, you could modify the table and it will be reflected in your select query.

A warning message in the Inbound part of the IDOC

Hi all,
A warning message is being displayed for the Inbound part of the IDOC.
Here is the message.
No filters , No conversion , No version change .
IDoc successfully processed in the ALE layer
    The IDoc has passed through the ALE layer successfully and can now be
    passed to the application. This transfer is either done online or as a
    background job, depending on the settings in the partner profile.
    If there are no further status records, the IDoc waits for the next run
    of the transfer report to the application.
    Success or failure when passing the IDoc to the application is
    documented in the subsequent status records.
Actions in the ALE layer
    The parameter 'No filters' indicates whether the processing in the ALE
    layer led to segments of the inbound IDoc being omitted. The important
    criteria here are the settings in the segment filter and in the
    distribution model for this sender.
    The parameter 'No conversion' indicates whether field values were
    converted in the ALE layer. This is the case if the IDoc contains
    organizational units to be converted, or if the ALE conversion tool for
    this sender is activated.
    The parameter 'No version change' indicates whether the IDoc was
    converted into an earlier version of the IDoc type. This happens if the
    IDoc type of the sender is different from its own IDoc type.
I have checked all the necessary Config settings and all of them are in place.
Your help on this will be highly appreciated.
- Surya.

Hi,
The IDOC may have successfully passed through the application, but check whether the status of the IDOC is changed to 53.
No filters, No conversions, No version change
occurs when the IDOC is not processed fully.
It may have stopped the processing without raising any error...
Check the program, whether there is any piece of code which stops the processing of the IDOC without changing its status to 51.
Sharin.

Error :Maintain pricing conditions for the material for the excise invoice

Hi
i have maintained excise data for material, after that i have created scheduled agreement with lp and with 0 value private and dummy tax code and delivery schedule is released. Now when i do the goods receipt i am getting error " Maintain pricing conditions for the material for the excise invoice date
Message no. 8I629" can some body can help me.
with regards
Narendra kumar

Hi,
goto tcode fv11 u have to maintained the condition.
first enter the condition type like jmop -
then enter, next screen u have the select the below comination.
select the plant/vendor/material base u have to maintain the conditions.
Thank's
MVS

Multiple conditions for the same button.

Is there any way you can have multiple condition (same type of the condition).
I have button that I would like to hide it at different stages.
For example I would like to have a button (Submit) which will be visible when
Status = Draft
Condition Type Value of Item in Expression 1 = Expression 2
P9_X_STATUS
Draft
and when also when userRole = author
Condition Type Value of Item in Expression 1 = Expression 2
P9_X_USER_ROLE
Author
Robert

Hi,
It would depend on when the fields get their values into the session. They may be below the button on the page but if they have a value in the session then the button's condition will see this.
If, however, you have only used a Default Value setting for the item, the value may not be in the session (even though it may be displayed on the page), so the button will not know about this value. In these cases, I set the default value using a page computation for that item that runs "On Load Before Header" and is conditional on the item being null. That puts the value into the session for other items to use if required.
Andy

How to insert a condition in the Graphic Window of a SAP Script ?

Hi,
I need to give a condition inside the Graphic Window for printing the Logo in the SAP Script. Now, my problem is that the Graphic window is only opening in Display mode. How to make it editable and insert a condition in it?
OR
Is there any other way to do it?
Please Help.
Thanks in Advance.
-VRU

Hi
I got your point. I'll provide you solution
In the logo window goto coding part by pressing F9 and give your coding as
IF &BKPF-BUKRS& = 'COM1'
INCLUDE GSPL OBJECT GRAPHICS ID BCOL LANGUAGE DE
BITMAP 'LOGO1' OBJECT GRAPHICS ID BMAP TYPE BCOL
ELSEIF &BKPF-BUKRS& = 'COM2'
BITMAP 'LOGO2' OBJECT GRAPHICS ID BMAP TYPE BCOL
ELSEIF &BKPF-BUKRS& = 'COM3'
BITMAP 'LOGO3' OBJECT GRAPHICS ID BMAP TYPE BCOL
ELSEIF &BKPF-BUKRS& = 'COM3'
BITMAP 'LOGO4' OBJECT GRAPHICS ID BMAP TYPE BCOL
ELSEIF &BKPF-BUKRS& = 'COM4'
BITMAP 'LOGO5' OBJECT GRAPHICS ID BMAP TYPE BCOL
ENDIF
<b>Note:</b>But you have to upload all your logos in se78 then only you can upload and give conditions for this
Regards
Pavan

How to make repricing for specific conditions at the time of billing?

Hello
I'm SD Pricing person. Let me ask here experts below my concern.
In EU countries, there is recycling fee in sales of electronics or Note PC with batteries....to keep our earth clean.
So when customers buy such products, they have to pay more as recycling fee including invoice amount.
My question is... we want to make repricing for recycling conditions when the billing is created.
Based on our configuration, recycling condition is not defined as a kind of tax condition.
So this value is just copied from sales order.
(pricing type in copy control is 'G' which means repricing for tax condition.)
In this situation, we want to make repricing for those conditions during operating system.
Is there any easy way to cover this?
As I think, this is not easy because the system is already operated.
To change condition attribution is really risky. If we dare do, we have to migrate all open orders.
So I want to put this way to the end of my choice.
For this requirement,
1. We have to change condition class or category or calculation type in order to be repriced based on pricing type 'G'.
(ex. Set the condition category as 'I' inter-billing or 'L' always repricing.)
But transaction data are created now and all open orders will be affected.
2. To create new conditions are not easy because these conditions are mapped to the CO-PA value field and the values are posted in FI doc.
3. To change pricing type in copy control is almost impossible because of the impact.
What can I do this in this situation?
What I want to do is just to make repricing for specific conditions at the time of billing in case that pricing type of copy control is 'G'.
Thank you in advance.

Let me ask agagin to all experts.
I want to make A condition to be repriced at the time of billing.
For this, I have to set condition category as 'L' (Generally new when copying).
But I do not want to do in that way becauuse I am maintaining big operated system now.
In addition, though I migrate open orders after changing config. as 'L', it is almost impossible for use to migrate because we have more than a thound open orders per a DAY as Globalized system.
That is why I am asking.
Simply I can create new condition but as I mentioned, there are various recycling fee so we already created about 10 conditions. And this recycling conditions are linked to REA package of SAP. So creating another 10 more conditions can not be a way for us.
At last, what I want is not to be shown this condition only in billing doc.
'A' condition should be displayed in both Sales order and Billing doc.
And simultaneously, when the billing is created and if user changed 'A' condition master, then new value which is different from sales order have to be reflected in billing doc.
Thank you in advance.

How Can I Change the Where Condition In the First SQL Query?

SELECT IND_SSN, BEG_SVC_DT, END_SVC_DT,
TRUNC(MONTHS_BETWEEN((TO_DATE('19'||END_SVC_DT,'YYYYMMDD')),BEG_SVC_DT)/12),
mod(trunc(months_between((to_date('19'||end_svc_dt,'YYYYMMDD')),BEG_SVC_DT)),12),
DECODE((SUBSTR(END_SVC_DT,5,2) - SUBSTR(BEG_SVC_DT,1,2)+1),-1,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-2,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-3,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-4,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-5,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-6,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-7,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-8,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-9,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-10,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-11,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-12,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-13,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-14,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-15,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-16,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-17,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-18,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-19,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-20,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-21,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-22,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-23,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-24,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-25,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-26,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-27,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-28,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-29,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-30,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
-31,((SUBSTR(END_SVC_DT,5,2)+ 31) - SUBSTR(BEG_SVC_DT,1,2)),
30,0,
(SUBSTR(END_SVC_DT,5,2) - SUBSTR(BEG_SVC_DT,1,2)+1))
FROM SVC_OCCURRENCES
WHERE end_svc_dt not in ('PRESENT')
AND SUBSTR(END_SVC_DT,1,1) IN '9'
AND SUBSTR(END_SVC_DT,5,2) NOT IN ('31')
and (SUBSTR(END_SVC_DT,5,2) - SUBSTR(BEG_SVC_DT,1,2)+1) not in ('30')
UNION
SELECT IND_SSN, BEG_SVC_DT, END_SVC_DT, NULL, NULL, NULL
FROM SVC_OCCURRENCES
WHERE SUBSTR(END_SVC_DT,1,1) IN 'P'
The above code works fine and I get the correct numeric values from the SQL
query when the varchar2 end_svc_dt field is numeric however if I have encoded
the word 'PRESENT' in the varchar2 end_svc dt field the SQL query aborts at
the last statement in the WHERE condition. The beg_svc_dt field is a Date field.
and (SUBSTR(END_SVC_DT,5,2) - SUBSTR(BEG_SVC_DT,1,2)+1) not in ('30')
I get the following error message
ERROR ORA-0722 INVALID NUMBER
I encode the word 'PRESENT' in a varchar2 end_svc_dt field on an Oracle form. This is the only word that can be encoded.
Is there some way that I can bypass the last statement in the where condition and
compute the values from the SQL query without having the SQL query abort?
Eventually I want to do this in a report. I know that this sounds strange but can it be done?

The above code works fine and I get the correct
numeric values from the SQL
query when the varchar2 end_svc_dt field is numeric
however if I have encoded
the word 'PRESENT' in the varchar2 end_svc dt field
the SQL query aborts at
the last statement in the WHERE condition.Ouch!
Storting dates in VARCHAR2 columns is bad practice, poor design and makes for horrible code.
The beg_svc_dt field is a Date field.
and (SUBSTR(END_SVC_DT,5,2) -
SUBSTR(BEG_SVC_DT,1,2)+1) not in ('30')If it's a date field then why on earth are you trying to SUBSTR it. SUBSTR = sub-string i.e. take a sub section of a string not sub-date.
I get the following error message
ERROR ORA-0722 INVALID NUMBERAnd you're surprised by this?
Is there some way that I can bypass the last
statement in the where condition and
compute the values from the SQL query without having
the SQL query abort?Store your dates properly, use additional flag columns for non-date information and code your SQL properly.
Eventually I want to do this in a report. I know
that this sounds strange but can it be done?Yes, most things are possible.

[svn] 1751: Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.

Revision: 1751
Author: [email protected]
Date: 2008-05-15 14:21:43 -0700 (Thu, 15 May 2008)
Log Message:
Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
QA: No - customer verified the fix.
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/MessageService.java

If you create a metadatatype with a single metdata block, and you reference that in your vm/cm cell attribute using a *one* based index, Excel seems to see the link and it honors it when saving the spreadsheet.
So, I ended up with something like:
<c ... cm="1"/> (I'm dealing with cell metadata, but the concept is equivalente to value metadata)
<metadataTypes count="1">
  <metadataType name="MyMetaType" .../>
</metadataTypes>
<futureMetadata count="1" name="MyMetaType">
  <bk>
    <extLst><ext
uri="http://example" xmlns:x="http://example"><x:val>87</x:val></ext></extLst>
  </bk>
</futureMetadata>
<cellMetadata count="1">
  <bk><rc
t="1" v="0"/></bk> 
</cellMetadata>
Hope this helps.

Price Condition at the Header Level

Dear SAPfans,
Can we set the pricing procedure at the header level of sales order,
i would like to configure the rounding mechanism work on the header condition on the sales order, can it be done thru pricing procedure ?

Hi,
You can make condition type either header or item level.
header level coniditon type doesnt have access sequence and you generally enter the value manually.
You can use this condition type in Pricing procedure.
Check all about Condition type in V/06
Hope this will help.
Reward Point if helpful.
Thanks,
Raja

User Exit / BAdI to update the pricing conditions of the Purchase Order

Hello SAPients,
This is my requirement:
"Copy the Pricing Conditions from the Shipment Cost Document (VI01 / VI02) to the automatically generated Purchase Order".
I'm using the enhancement V54U0002 (Function Module EXIT_SAPLV54U_002) to EXPORT the values of the Pricing Conditions to memory and I have used the enhancement MM06E005 ( FM EXIT_SAPMM06E_006, 007, 012, 013, 014, 016, and 017) to IMPORT the values from memory and store them in TKOMV. But, when the PO is generated the values don't stay, they are always changed with the standard PBXX pricing conditions.
My question is: Does anyone know the User Exit / BAdI that I can use to change the Pricing Conditions of the Purchase Order?
<<removed_by_moderator>>
Thanks!
Edited by: Vijay Babu Dudla on Jan 14, 2009 11:08 PM

>
kartik tarla wrote:
> check this badi
> ME_PROCESS_PO_CUST
>
> and the following user exit
> Goto-> include RV61AFZA then search for
> USEREXIT_PRICING_RULE see if its helpful to u.
Hello Kartik / SAPients,
I tried with ME_PROCESS_PO_CUST but didn't work. The system doesn't execute that code. Any other idea would be greatly appreciated.
Thanks.

How can I have the pricing conditions at the item and header level of the d

How can I have the pricing conditions at the item and header level of the delivery? There exist "condition" tabs both the header and the item level of the delivery but the contents of the tabs are empty. I'll be happy if you can help me. Thanks in advance....

Hi
If you want to have the pricing procedure at delivery level then you need to assign a pricing procedure at delivery level also
Just go through the path to maintain the pricing procedure at delivery level.
IMG -> Logistics execution -> Shipping -> Basic Shipping Functions -> Pricing -> Pricing Procedure. for Delivery.
But can you be more clear if the above one is not your query ?
Regards
Srinath

I am unable to get past the Terms and Conditions in the new update. I have hit agree several times but can not get past that part. What do I do next?

I am unable to get past the terms and conditions part of the upgrade. I have hit agree several times. What do I do?

Scroll down to the bottom of the terms and conditions, then the Agree button will light up and you can proceed.

Should the condition in the loop step

Should the condition in the loop step in the integration process(BPM) be = or not= ?I need to do the following>>perform certain operation only when the container value is less than 3 Else then get out of the loop.
Regards,
Mansi

The loop step in ccBPM implements a while loop.
So, while count not = 3, it will be executed.
Once the counter reachs 3, the loop will be terminated.
Regards,
Henrique.

Function-based Index and an OR-condition in the WHERE-clause

We have some problems with functin-based indexes and
the or-condition in a where-clause.
(We use oracle 8i (8.1.7))
create table TPERSON(ID number(10),NAME varchar2(20),...);
create index I_NORMAL_TPERSON_NAME on TPERSON(NAME);
create index I_FUNCTION_TPERSON_NAME on TPERSON(UPPER(NAME));
The following two statements run very fast on a large table
and the execution-plan asure the usage of the indexes
(-while the session is appropriate configured and the table is analyzed):
1)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%';
2)     select count(ID) from TPERSON where NAME like 'Mil%' or (3=5);
In particular we see that a normal index is used while the where-clause contains
an OR-CONDITION.
But if we try the similarly select-statement
3)     select count(ID) FROM TPERSON where upper(NAME) like 'MIL%' or (3=5);
the CBO will not use the function-index.
(This behavior we only expect with views but not with indexes.)
We ask for an advice like an hint, which enable the CBO-usage
of function-based indexes in connection with OR.
This problem seems to be artificial because it contains this dummy logic:
     or (3=5).
This steams from an prepared statement, where this kind of boolean
flag reduce the amount of different select-statements needed for
covering the hole business-logic, while using bind-variables for the
concrete query-parameters.
A more realistic (still boild down) version of our prepared select-statement run in
SQL Plus:
define x_name = 'MIL%';
define x_firstname = '';
select * FROM TPERSON
where (upper(NAME) like '&x_name' or ( '&x_name' = ''))
and (upper(FIRSTNAME) like '&x_firstname' or ('&x_firstname' = ''))
and ...;
In particular we dont refernce the tablecolumn , but the QUERY-Parameter
yield the second boolean value in the or-condition.
The problem is that this condition ('&x_name' = '') dont use any index.
thanks a lot for spending your time with this problem

Try
SELECT /*+ RULE */
as your hint. I don't have the book with me, but this last weekend I read a section about your very problem. The book was a Oracle Press gold cover about Oracle 8i Performance tuning. If you e-mail me I can quote you the chapter when I get home Friday.

Inbound Condition in the PO

Similar Messages

Maybe you are looking for