RE: [ubl-dev] Specifying backorder in OrderResponse

[Kenneth Gray <DKKGR@coloplast.com>]

Thanks for your reply.

That sounds reasonable.  I guess then we would also have to agree on how to interprete  or:OrderResponse/cac:OrderLine/cac:LineItem/cbc:Quantity in conjunction with the LineStatusCode.  

/Kenneth




-----Original Message-----
From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] 
Sent: Thursday, March 24, 2011 6:24 PM
To: ubl-dev@lists.oasis-open.org
Subject: Re: [ubl-dev] Specifying backorder in OrderResponse

At 2011-03-24 03:01 -0700, Kenneth Gray wrote:
>I'm looking for a guideline and hopefully an example of useage of 
>the OrderResponse to inform that an item is in backorder.  Can't see 
>it described anywhere.

Thanks for your post!

I think the place for this is:

   or:OrderResponse/cac:OrderLine/cac:LineItem/cbc:LineStatusCode

As there is no recommended code list member for backorder in the 
OASIS-supplied code list[1], you would divine one for your community 
of users.  Then for validation purposes there are a number of steps 
to take to replace the value validation with the appropriate 
XSLT.  The steps include creating a new code list in genericode, 
specifying the union of the UBL list and the custom list in a CVA 
file, and then creating the XSLT from the CVA and genericode files.

But I'd like to hear from other members of UBL-Dev if they agree or 
disagree with where and how back orders are specified.

Thanks again!

. . . . . . . . Ken

[1] 
http://docs.oasis-open.org/ubl/os-UBL-2.0/cl/gc/default/LineStatusCode-2.0.gc

p.s. since back-ordering is a common concept, I wonder if it makes 
sense to add that as a line status in the committee-supplied code 
list ... but not, I suppose, if line status is used in other contexts 
where back-order isn't applicable ... in that case it still makes 
sense to have a separate code list and only specify the union of the 
two lists where back-ordering is applicable in addition to the other 
line status


--
Contact us for world-wide XML consulting & instructor-led training
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/u/
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal


---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org