Unable to assign value

, ,
1

I was trying to assign certain attributes such as transaction, standard from a BIZdoc containing EDIdata. I have initially tried variable substitution since this is s runtime strucutre. When that failed I tried creating a dummy bizdoc based on the runtime strucure, assign the bizdoc to that structure then try to map the values from that structure. Both cases, I can see the value is available during runtime but I was unable to assign it to a variable.

The variable strucure is like “bizdoc/DocType/standard”. I managed to get around this by using some EDI functions, but I am curious why I have been unable to read them. Thanks for any info.

BTW, I am using wm6.1

2

SR,

If you do variable substitution and extract those info from the bizdoc,it should work please check if there is any typo or may be casesensitive (check exact name in the pipeline),and you have to check the variable substition check box (this simple thing happens)

HTH,
RMG.

3

RMG,

I have checked for those things. I am able to read other variables which are part of standard bizdoc structure. It’s not spelling mistake either. I have copied the strcture from pipeline and did it multiple times too. I suspect there must be something different about the way EDI attributes are stored. But I could not find any such information in any document.

Thanks,
Sridhar

4

RMG,

I have checked for those things. I am able to read other variables which are part of standard bizdoc structure. It’s not spelling mistake either. I have copied the strcture from pipeline and did it multiple times too. I suspect there must be something different about the way EDI attributes are stored. But I could not find any such information in any document.

Thanks,
Sridhar

5

SR,

Its wierd,we have used the same technique and it worked for us,anyways do some more research on that but there is not special thing involved using EDI attributes that is sure.

some cases these variables will be outside of bizdoc,check this too…

goodluck,

6

WM provdies services to extract this information:

wm.b2b.editn:getStandard -> document standard
wm.b2b.editn:getTransaction -> document transaction
wm.b2b.editn:getVersion -> document version

We always use these. They each take as input the bizdoc and give back a string.

7

Thanks. I have used the services. I probably should have mentioned the names in my first post. But I am still wondering why those variables are unreadable in the first place.

8

Thanks. I have used the services. I probably should have mentioned the names in my first post. But I am still wondering why those variables are unreadable in the first place.

9

Hello,
you seem to be double posting, you don’t have to double the confirm button. I am not sure if you get the values you want. If you do then good and it may be good to use for the future as those would work alongside changes to the bizdoc structure (Single point of correction).

If you want to test what to bizdoc gives access to, a check is to make a cascading branch to how far you can reach into the structure. It may be that you are trying to access an array with a branch and not using an index -> [?] or you are working in a loop and only have a single variable (so it won’t loop without an array with a ‘lengh’ > 0).

Please becareful of the extra data structure put on the pipeline by TN but not exposed as part of the parameter signature. if you add formats they may not provide data in that structure. We use x12 and edifact and that is the case sometime for editn_xtn and I forget the other structure.

10

Sorry about the double posting. The net was acting crazy in my office. Yes, I have got the values I wanted. I am just trying to understand why this happens. Also it may be useful for other variables.

Also there was no array involved, I have checked that.

I’ll try the suggestion regarding extra structures.

Thanks

11

HI SR,
We have faced the same problem here. But solved it. the mistake on our part was about the case sensitiveness of the bizdoc variable that’s it. Rest everything seems to be working fine.

Regards,
pradeep

12

SR,

Please check the case sensitive when doing variable substitution,since this happens when overlooking.

sorry if we are repeating the same thing from the beginning.

HTH,
RMG.

13

Hi RMG,

As I have mentioned before, I have copied the name from the results, specifically to avoid spelling errors. Yes, I know that can happen easily, but I have checked for all these things.

In fact you can check reading the variables ‘bizdoc/DocType/version’, ‘bizdoc/DocType/standard’ or ‘bizdoc/DocType/transaction’ if you are using any EDI transactions.

14

SR,

I have used this before and it worked for us,so i am stressing on that to make sure.

let c if anybody has other clues.

15

Hello,
I know your concern. I was just testing around and I saw this:
wm.b2b.editn:getICDetail
It gives back the “editn_env” structure (the one I forgot in my previous post). I saw that it gave a nice set of information, albeit alot of it redundant. It does allow you to have a structured look at some of your data and only needs to have a text string passed in (Full envelope). So like I said before, I do not trust now using a structure that does not have design time addressable components, this may give you some of your values in a clean fashion.

One other thing is you may want to try to add the variable to the structure at the position you are looking for. You may have to add documents and strings to the input side of pipeline at that map step. This may work better than using varSub. I just usually favor using built in services when possible, second to use map steps with visual lines drawn with substring or concat to break or build strings, third I use varSub to get at explicit sections, and I have a custom “getDocumetElement” service that traverses the data for the first available instance of a string or structure or object.