Outbound EDI validation

, ,
1

I am doing 810 x12 4010 version for outbound.
I am facing this problem.
Afetr i convert idoc to EDI string , i am validating edistring in
convertToValues service.when i mention noEmptyTrailingFields in convertToString service to ‘false’, the convertToValues service is generating errors.But when i dont use noEmptyTrailingFields or set to ‘true’. there are no errors.even i did not find that error code in the error message guide.
The error looks as follows.

Error Message: [FFP.0011.0003] Unexpected element. The record or composite data contains more fields than are in the record or composite definition.The EDI segment which have the problem is: REF05.
Like this it is giving for REF06, REF07,REF08,REF09.
My edi string is looks like this.

ST8100374~
BIG2005020290029306490527119391DI~
REFPK8003470486~
ITD01322530~
DTM01120050202~
FOBPPOR~
IT125EA48VP6E040L0BP308328~
TDS120000~
CTT1~
SE10*0374~

One more thing is if i tested same thing with another partner without REF segment its working fine.

Any help should be highly appreciated.

2

Ramesh,

Check the 810 dictionary/schema whether those REF segment fields are not nullable fields or mandatory or service is validating etc…so that you will know exactly whats going on when you set the “noEmptyTrailingFields” to false and try setting it to true also.

HTH,
RMG

3

Also sometimes the combination and dependent of fields should exist in the runtime validation like REF05 needs to be populated when REF06 exists or it should not exist etc…

Based on the error i am still wondering what could be the exact root cause,but give it a shot checking the x12 810 using specbuilder tool.

Regards,

4

Hi RMG,

thanks for your response.
The problem was solved.
The solution ( i dont know whether it is right or not) is in the dictionary for REF segment i made checkfields = “false”.
Then it is not giving any errors.before it was “true”.

Any how Thanks for your suggestion.

5

As long as you dont require the REF segment to pass the validation it is fast resolution.But you should be careful to migrate the same change in all your existing environments(QA,UAT,Prod etc…).

Goodluck,