Validation req no.2

Hi,
I want to write a validation on Identification no.
The format is like first 3 are numer from 0 to 9 and then there are alphabets any from a to Z.
Help!!
Brad

Hi ,
U can write in the following ways:
1) If there is not a space b/w nos and alphabets
HAS_ALL_CHARS( MID(Id no.,1,3),"0","9") AND HAS_ALL_CHARS( MID(Id no.,3),"a","Z")
2)If space is there and no of alphabets are not constant:
HAS_ALL_CHARS(MID(Id no,1,3),"0","9") AND HAS_ALL_CHARS( MID(Id no,FIND(Id no," ")),"a","Z")
Hope this may help u .
I have not run this expression.Kindly check them if they are working
Rgds
Ankit

Similar Messages

Validation req no.1.

Hello ,
We have a req to check if a field (prdt no.) is not null and also its lingth is 12 .It is of specific format having 3 uniq nos then a "-" then 3 nos then "-" and then 4nos.total length 12.
How to implement ?
Kindly help!!
Brad

Hi .
Just try this
(i have not check this in data manager) :
IS_NOT_NULL(Product no.)AND (((LEN(Product no.)= 12)AND ((FIND(Product no.,"-")= 4)AND (MID(Product no.,8,1)= "-")))
U can check the properties from page no.240 of mdm data manager guide to understand the feature of each
Just try and check ,may be i have missed some brackets !!
Hope it may work!!
Rgds
Ankit

Field Validation on Custom Obj. 4: Value of one field making other Req.

Hello All,
I have been working on a field validation problem for a while. I have a custom Picklist on CO4. This picklist has two values YES and NO (a checkbox does not meet requirements). What I need to do is If Picklist='YES' then FieldA, FieldB, and FieldC are Required else they are not required. FieldA = Text (short), FieldB = Date, and FieldC = Currency. I've tried numerous ways to validate on Fields A, B, and C with statements like IIf(Picklist=LookupValue(Picklist,"YES"),FieldA<>NULL,FieldA) or IIf(FieldValue(Picklist)="YES",FieldA<>NULL,FieldA) etc... these were just my latest attempts at this point I'm jsut trying random things to try to get it working. I am probably using incorrect syntax (even though it passes the sytax checker). If anyone has any suggestion let me know. Also if I haven't made clear what it is I'm attempting to do let me know and I'll try to clarify.
Thanks,
Z

Hi,
if I understand correctly, you want this functionality:
If Picklist = NO => it doesn't matter what values are contained in Field A, B and C.
If Picklist = YES => Field A is not null and Field B is not null and Field C is not null
To trigger the validation when the picklist value changes then you have to configure the Field Validation for the Picklist:
[<Picklist>]=LookupValue("Picklist","NO") OR ( Len([<Field_A>])>0 AND Len([<Field_B>])>0 AND Len([<Field_C>])>0 )
You have to put the validation also on Field_A and Field_B and Field_C, because in case of an update of , let's say, Field_B, you should prevent that Field_B is blanked.
If someone updates only Field_B and he doesn't change the value of the Picklist, the validation expression put on the Picklist is not evaluated.
Simona

Module pool screen I/P Validation info req?

hi
please tel me how to validate a screen I/P in module pool.
i had a screen:1000.
there in an I/P date from: date to:
user wants,if any one puts date to < date from,there shd be an error msg,i had done it,but after it,all other fileds are disabled,but i want after error msg,it shd allow me to do the modification.
please tell how to do.
vipin

Keep the validation in one module, say, m_validate.
write the following code in screen flow logic.
CHAIN.
FIELD: date_from,
date_to.
MODULE m_validate.
ENDCHAIN .

Unfirmed purchase reqs not getting cancelled in the background MRP run

Good morning,
The system has created Purchase requisitions for 2010 due to the setting in the MRP run. we want to change it to planned orders outside the Vendor lead time and when i run a REGEN MRP with setting 2 (Purchase requisitions in opening period) its not happening. When i run indivudual MRP with MD03 with the same setting its alright, purchase requisitions are deleted and its converted into Planned orders. Can anyone please throw some light on to make backgrouond MRP run delete the Purchase requisition and create planned orders.

Jags,
You must delete the offensive PRs first. Regardless of the MRP settings, MRP will still decide that the PRs are valid and will leave them alone. It will not 'change' them into planned orders.
Run Regenerative MRP with your new settings (Create purchase reqs as '2') but also run your MRP in planning mode '3', delete and recreate planning data. It will delete all existing unfixed purchase requisitions, and then run MRP.
Rgds,
DB49

Validation at the network level

Hi Experts,
I am doing the validation for the network at the header level for the resposible cost center field.
I am giving Prerequiest as
Req.cost center = 'X'
Check as
i am not entering anything in the check condition
Message
I am entering the message & message type is error.
initiation of this validation is i want to check that any value is entered in the Req.cost center field. (Making this field as a manditory).
But after doing that it is not checking in my cj20n transaction.
can anybody suggest me wht is the problem.
Thanks & regards
Raman T S

Hi,
In validations 'X' doesn't mean alphanumeric, it means alphabet X only. That's why system is not giving you any message.
You need to put validation check as Resp. Cost Center <> ' '
which means it shouldn't be blank.
Regards,
Harsh.

BOM Valid Date

Hi,
While creating BOM due to some human error we took wrong valid date.Now i want to change it.
Please suggest me the T-code or any customization to change the same.
"I am online"

Dear Pawar
This are the basic IMG settings in order to used the engineering change management
features.
x refers to a tick.
First setup the control data in OS54.
Revision sections
Fields :-
Revision level active            x
Ext. revision level              x
Higher revision level            x
Object Management Record sections
Fields :-
Object maintenance               x
Assign alternative date          x
Overide value/assignment date sections
Fields :-
Only with leading change mst.    x
Setting the Revision level active is to activate the engineering change management for
material master. If you do not want the engineering change management for materials,
remove the tick.
With a tick in "Higher revision level", the new revision level has to be always higher
than the old revision.
Secondly, setup the external number range in OS53.
If you use the internal number range, then remove the external number range.
Third, define the status for the change master records in transaction SM30 - V_T419S.
Change No.     Chg        Date Chg     Dist. Lock      Description
Status         Poss
1             x            x             ' '         Active
2            ' '          ' '            ' '         Inactive
3            ' '          ' '             x          Locked
Fourth, define modification parameters for the BOM in OS27.
Fields :-
BOM Validty Maint.               x
EC Management Active             x
History Requirement             ' '
Unit Piece                      PC
The rest of the fields are blank.
If the History Requirement is tick, every time during creation of the BOM, SAP will
prompt your for an ECN number as is compulsory.
Lastly, define fields selection for routing in OP5A.
PP task lists: initial screen -> Change number -> Transaction code -> Tick Req.
Setting the Transaction code fields Required indicate that you have make the ECN number ........
Hope this will help you one of our friends gave me this
Pavan

End of Valid Logistic Calender error while creating Sales Order

Hi,
While creating Sales order in VA01 the following error message comes for particular material code for a particular site only:
24.01.2202 date comes after end of valid logistics calendar. (Please
correct)
Message no. 61062
Can anyone suggest on the same.
Regards
Nilofer

Hi,
The input value given in Sales order is " Req Delivery date: 31.03.2012", but the error comes with the below date such as
"24.01.2202 date comes after end of valid logistics calendar.(Please correct)"
We also face one more error such as
" Incorrect index structure for table XMVERF_POS/0000224110/000040 ".
From where system is taking 24.01.2202 date?

Validation for Profit Center and Trading Partner

Hi Gurus,
Please help me in creating validation for Profit Center and Trading Partner.
I want system to give an error if we use Trading Partner related to particular profit centers.
Please revert asap.
Thank You

Hello,
Please use T.code OB28 and select the call up point 2.
Than go to Prerequisite in expert mode and say
Prerequisite : BSEG-VBUND <> ' '
Check: BSEG-PRCTR = ' '
Error Message.: xyz
I have created Validation understanding if someone gives Trading Partner and also Profit center while posting a doc than it will generate an error message.
however if you have some diff req please change it accordingly/ take Abapers helps if not very clear.
I hope this helps
Regards
Shireesh

Downpayment Request Validations

Hi,
Iam working on adding more validations to Downpayment request (f-47) using the function exit EXIT_SAPLFMR4_002. One of the validation says "WBS value on request matches PO value". Once we choose the PO value, the WBS value is automatically populated.Currently WBS field is an editable field. Is it possible to make it as Display field? If i make it as display field will the value be saved backed to the table?
I tried through the configuration OB41. We have only 3 options there 1. Supress 2. Req Entry and 3. Optional entry. So if i choose the options Supress, the WBS value is not getting saved back to the table BSEG after the transaction is saved.
So how do i make this WBS field as non-editable and the value gets saved to the table?
Thanks.
Rajee

Hi,
As per my knowledge, Downpayment Request is a Noted Item (Single Line Item), it is just request not receipt.
So, system won't show you the Bank details. Once you received or paid with reference to that request that time Bank details will be shown.
Best Regards,
Chandra

B2B-51507- Payload validation error - 11.1.1.7 Latest Version

Anuj/Nitesh (B2B Gurus)
I am facing a problem when Posting the message from SOA to B2b (XML->EDI) using the B2b Adapter.
Flow is : Ebusiness->PLSQL->AQ->BPEL->B2B. Once the message is posted to B2b It is throwing the following Error.
But I am passing all the mandatory and Optional Parameters.
Tried the Following Threads, But No luck. I am passing all the Mandatory Parameters.
How to map Internal-Properties in XSLT.
Oracle B2B Payload Validation exception
Scenario - 1 (Success No Errors , Output Does not Contain PO Details)
Disabled the Validate flag in the Partner Agreement for the B2B Document.
Verified the B2b Wired Message, Output got generated but without the PO information I am passing from BPEL.
Scenario - 2 (Error )
Enabled the Validate flag in the Partner Agreement for the B2B Document. The system is generating an error and throwing list of errors.
Error
Id
C064016C14103689486000005559CD14
Message Id
C064016C14103688C7F000005559CD0F
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
ABC
Receiver Type
Name
Receiver Value
TEST123
Sender
ABC
Receiver
TEST123
Agreement Id
EDI_850_tpa_Lt7763342564515893374
Agreement
XXX_EDI_X12_4010_850_Outbound
Document Type
850
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
9/9/2013 10:48
Receive Time Stamp
9/9/2013 10:48
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
5471
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Sep 05 11:51:44 CDT 2013 - 4
Collaboration Id
C064016C14103688E1A000005559CD13
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : Error reporting limit exceeded. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A functional group code mismatch was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A transaction ID mismatch was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered.
Error Brief :^M
Error reporting limit exceeded.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Description: Payload validation error., null, null, null, null, C064016C140EF31BFCA000005559CC
A4, null, null, 1258, B2B-51507, null, null, null, null, null, 2013-09-05 12:35:49.092, null, ^M
Error :^M
Analysis halted after 101 error(s) (Limit for Transaction is 100). Large numbers of errors usually indicate that the same error is repeatedly encountered in multiple segments or transactions. Fix the repeating error and resubmit the test to obtain further results.^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 1{br}{tab}Characters: 210 through 212^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 2{br}{tab}Characters: 247 through 257^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 3{br}{tab}Characters: 292 through 294^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 4{br}{tab}Characters: 329 through 339^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 5{br}{tab}Characters: 374 through 376^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 6{br}{tab}Characters: 411 through 426^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 7{br}{tab}Characters: 463 through 465^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 8{br}{tab}Characters: 502 through 517^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 9{br}{tab}Characters: 552 through 558^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 10{br}{tab}Characters: 593 through 597^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 11{br}{tab}Characters: 632 through 633^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 12{br}{tab}Characters: 668 through 673^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 13{br}{tab}Characters: 708 through 717^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 14{br}{tab}Characters: 752 through 753^M
Thanks
Rao.

Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi.

Payload validation Error - Outbound flow

Hi,
I am trying to create an outbound flow to send a X12,4010,810 document to a trading partner.
Got the error - Payload Validation error.
Payload is as below
<?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
Can someone suggest what is the problem with this payload.

More detail --
Below is the message that is displayed in Oracle B2B Reports -> Business Message
Id
7F000001144BE0AB3A100000231A6860
Message Id
11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
OracleServices
Receiver Type
Name
Receiver Value
MarketInc
Sender
OracleServices
Receiver
MarketInc
Agreement Id
OS_MI_X12_4010_810_OutboundInvoiceAgr
Agreement
OS_MI_X12_4010_810_OutboundInvoiceAgr
Document Type
IN
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
Mar 13, 2014 7:42 PM
Receive Time Stamp
Mar 13, 2014 7:42 PM
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
2344
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Mar 17 08:30:33 CDT 2014 - 8
Collaboration Id
7F000001144BE0AB37E00000231A6850
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Machine Info: (XXXX) Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : XEngine error.
Application Message :
Id7F000001144BE0AB22400000231A6820Sender Id TypeSender ValueOracleServicesReceiver Id TypeReceiver ValueMarketIncDocument TypeINDocument Definition810_DefDocument Protocol NameEDI_X12Document Protocol Version4010Refer To Application Message IdRefer To Application Message IdApp Conversation IdApp Message property{fabric.enterpriseId=-1, b2b.documentProtocolVersion=4010, b2b.documentDefinitionName=810_Def, b2b.messageId=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, MESH_METRICS=null, b2b.messageType=1, tracking.parentReferenceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E:954F6910AB1111E3BF8A5F99BC4D6B4E:oneway, tracking.compositeInstanceId=20012, tracking.ecid=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, b2b.toTradingPartnerId=MarketInc, b2b.fromTradingPartnerId=OracleServices, tracking.compositeInstanceCreatedTime=Thu Mar 13 19:42:55 CDT 2014, tracking.conversationId=snbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4., tracking.parentComponentInstanceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E, b2b.documentTypeName=IN}DirectionOUTBOUNDStateMSG_COMPLETEError CodeError TextError DescriptionCreatedMar 13, 2014 7:42 PMModifiedMar 13, 2014 7:42 PMMessage Size2344PayloadPayloadBusiness MessageBusiness MessageRetry Interval0Reattempt CountRemaining Retry0ECID11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfcComposite Instance Id20012Parent Composite Instance Idmediator:954F1AF0AB1111E3BF8A5F99BC4D6B4EConversation IdsnbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4.Domain NamedefaultComposite NameOSToMIOutboundInvoiceProjectComposite Version1.0Reference NameB2BOSToMarketIncOutboundUrl
Payload Storage :
<?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
I have set the following b2b headers in SOA before sending it to B2B outbound
Constant: 4010_810_Def Property: b2b.documentDefinitionName
Constant: 4010 Property: b2b.documentProtocolVersion
Constant: OracleServices Property: b2b.fromTradingPartnerId
Constant: MarketInc Property: b2b.toTradingPartnerId
Constant: 1 Property: b2b.messageType
Constant: IN Property: b2b.documentTypeName ( I defined my docuemnt with name 'IN')
Property: tracking.ecid Property: b2b.messageId

Unable to generate csr, Please use a valid file name

I've been attempting to generate a new certificate signing request on our Exchange 2013 server. In the past we've never had a problem but we seem to be stuck today. When we try to output the new csr to one of our network shares we see the following
error.
"Please use a valid file name when you run the New-ExchangeCertificate cmdlet on server server1 with the -RequestFile parameter. The file should not exist in target folder. Parameter name: RequestFile"
We've use this share location before without problems, the Exchange Trusted Subsystem has write intermissions on this location as described online but we still receive the error. I've tried creating new locations but haven't had any success.
Any suggestions?
Thanks

Hi,
We can access the Exchange Certificate Management UI through the EAC in Exchange 2013 by selecting
Servers and then Certificates to create a new certificate to have a try.
Alternatively, we can try the following command:
$Data = New-ExchangeCertificate -GenerateRequest -SubjectName "c=US, o=contoso inc, cn=server.contoso.com" -DomainName mail.contoso.com, contoso.com, autodiscover.contoso.com -PrivateKeyExportable $true
Set-Content -path "C:\Certificates\MyCertRequest.req" -Value $Data
Regards,
Winnie Liang
TechNet Community Support

Validation in ECC6.0

Hi there,
We are on SAP ECC6.0 and facing problem in setting the Validation.
The Validation is activated for Co Code in SPRO.
Requirement:
1. There are over 20 Company Codes.
2. Users of X Co Code should NOT be allowed to Post an Accounting Line Item on Y Co Code's Cost Center
Validation:
1. Pre-Requisite
BKPF-SNAME IN XUSERS - This is the Set Name with User IDs of X Company Code
2. Check
BSEG-KOSTL NOT IN XCC - This is the Set Name with Cost Center of X Copany Code
This is giving me Syntax Error
BSEG-KOSTL IN XCC - This is the Set Name with Cost Center of X Copany Code
BSEG-KOSTL = 'Y*' - This is the Set Name with Cost Center of X Copany Code
This is not giving syntax error but it is not working while doc posting
3. Message
Error
Can you please let me know where am I going wrong?
Thanks
Rob

Hi there,
I have done the Validations at Line Item level as under:
Pre-req:
BKPF-BUKRS = 'ABCD'
AND SYST-TCODE <> ''
Check:
BSEG-KOSTL >= '100'
AND
BSEG-KOSTL <= '199'
Message:
Error Message if any other Cost Center other than 100 TO 199 is tried to be posted for Company Code ABCD.
This validation is working fine in case of postings to GL Accounts. However, for any Balance Sheet account I get an ERROR even if the Cost Center for P&L hits say for ex 105.
Please help.
Thanks
Rob

How do I get a valid keystore file?

I want to self-sign my first Adobe AIR application and I'm
having trouble getting a valid keystore file. It says that it is
"not an X509 code-signing certificate". I am on Mac OS X and on a
terminal I tried to use openssl to make a certificate. This is what
I did:
$ openssl genrsa -des3 -out daniel.key 1024
$ openssl req -new -key daniel.key -out daniel.csr
At this point I didn't know how to use the CSR to get a
certificate, or the PKCS12 file that Adobe AIR needs. So I signed
up with a free CA (CAcert), gave them the CSR and they gave me a
certificate file. I saved it as "daniel.crt". Then I ran:
$ openssl pkcs12 -export -in daniel.crt -inkey daniel.key
-out daniel.p12
But when I tried to use daniel.p12 to package my application
ADT claimed that it was "not an X509 code-signing certificate":
$ adt -package -storetype pkcs12 -keystore daniel.p12 Foo.air
Foo-app.xml Foo.html lib
password: foo
not an X509 code-signing certificate
I hope someone here can help me. I just want to be able to
package a simple hello-world application. I want to self-sign it.
What do I do? I'm stuck! Any help would be really appreciated.
Daniel.

Aha! I found the solution:
$ adt -certificate -cn name key_type pfx_file password

Validation req no.2

Similar Messages

Maybe you are looking for