OASIS Universal Business Language (UBL) TC

 View Only
Back to discussions
Expand all | Collapse all

SV: [ubl-psc] Re: [ubl] RE: Uploaded Procurement model spreadsheets

  • 1.  SV: [ubl-psc] Re: [ubl] RE: Uploaded Procurement model spreadsheets

    Posted 08-24-2005 11:27 
     MHonArc v2.5.0b2 -->

















    ubl message
    







    [Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]
    


    







    Subject: SV: [ubl-psc] Re: [ubl] RE: Uploaded Procurement model spreadsheets
    







    



    



    Dear 
TC members
    

     
    

    During 
my review of the spreadsheets from Stephen, I found the folling issues we need 
to discuss:
    

     
    

    a) The 
placements and order of the new elements. What is the order of the new 
documentreferences, the new party types? Are the line items still the last in 
the documents.
    

    b) 
What partytypes need to be mandatory? Is it still the buyer and seller or is it 
the partytypes involved in the usecase, is it only the sender and receiver of 
the documents or should they all be left optional?
    

    c) 
With the extended procurement process the sender and receiver iare no longer 
always the buyer and the seller. This leaves us with a complicated business 
rules to find the ID of the receiver and the sender. Some may state that theese 
infomations is not relevant for other than the transporting layer, but in real 
life this is not true. UBL sets no requirements to the transporting layer and at 
Least in Denmark we also support transportation without header information, e.g. 
via FTP. In eFaktura the routing is based on an id called BuyersReferenceId (I 
my mind it should have been BuyerParty-> Id). Therefore I would like to 
suggest that we put in two new BBIE, called SenderId and ReceiverId for all 
documenttypes. This will make it a lot easyer to build programs to route the 
messages. The reason why I suggest them as BBIE and not process instructions is 
that we need to be able to reject documents without from these 
fields.
    

     
    

    Kind 
regards
    

     
    

    Peter
    

     
    

     
    

    
  
    -----Oprindelig meddelelse-----
    Fra: Tim McGrath 
  [mailto:tmcgrath@portcomm.com.au]
    Sendt: 24. august 2005 
  11:51
    Til: swebb@gefeg.com
    Cc: 'Stephen Green'; 
  ubl@lists.oasis-open.org; ubl-psc@lists.oasis-open.org
    Emne: 
  [ubl-psc] Re: [ubl] RE: Uploaded Procurement model 
  spreadsheets

    if it helps, my understanding is that all 
  entries in the procurement and common spreadsheets (and eventually also the 
  transportation spreadsheet)) will create one CAC and CBC schema - so i guess 
  that is one EDIFIX model as well. 

    also, please let us know what 
  the circular references are as they may need to be resolved.

    Sylvia 
  Webb wrote:
    
  
    Stephen,

I am having a temporary problem loading these spreadsheets into EDIFIX. The
problem is that it doesn't know if one or two data models should be created
with the Reusable and the Procurement Reusable spreadsheets. There seems to
be a circular reference. We cannot proceed any further until we get some
clarifications about what to do. 

Since the Procurement Subcommittee may not be able to discuss this before
the week is over, I will request that it be placed on the Atlantic TC
meeting agenda later today.

Regards,
Sylvia


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                
    
                                                
                                            
                                        

                                        
                                        

                                    
			

                                    
                                

                                
                                
    
                                
    
                            
		
                
        
    




            
        
    


	
    


    
    
         
    
    Related Content
    

        
               
                
                
                
                
                
        
    
    
    

    
        
    
		
        
	
    
        
    

						
						

						
					

					
					
					
				

			

			
    
				
			
    

			
			
    
                                                
    
                                                    Global message icon