Questions regarding DataModelling for incoming invoices

[former_member184588]

Hi,

I would like to make a NW GW Service for incoming invoices. I am following the guide: [Content Deleted June 2013]

Unfortunately I don't get the point with some things. And maybe the questions are really confusing because of my lack of knowledge.

- In the tutorial there is a reference from BANK_CTRY to the BANK_LIST->BANK_CTRY. In the BAPI_INCOMINGINVOICE_GETLIST I cannot find a reference to INV_DOC_NO and FISC_YEAR in the root. Is this a problem?

- I want to get the Headerlist and deselect the RETURN-Attributes. Then he tells me that RETURN is mandatory and if I am sure that I would like to deselect it. Is it okay or will this be a problem?

- Is it right that I Map the invoicedocnumber of my read operation to INV_DOC_NO from the List operation?

- In step 9 of the tutorial they say that I have to make the structure flat. But when I put my itemdata with cardinality 0..n to the root... it says for good reasons that this is not possible. Do I really need to put it as a flat structure? How can I get a list of line items from the nw gw service?

- If I don't think about the things mentioned above and continue... The system says that I need a key for my ACCOUNTINGDATA. But when I want to set the key it tells me that "Action is not allowed on a delegated key".

- Do I need two services? One for the Invoce and one for the invoiceitems to keep the structure flat?

Thanks a lot. Maybe someone can bring some light into the darkness.

Greetings, Vanessa

Message was edited by: Jason Lax

[goutham_nagarajnaidu]

Hi Vanessa,

Did you do the mapping i.e from data source (RFC) to Model properties.

if you had done then you can see the reference(mapping) in service builder.

in tutorial that reference means , when the query operation is executed from client.

BANK_CNTRY will have the values from that export parameter.

it is not a problem ,you can also do that mapping manually,that is a default mapping that is given in the tutorial you can also change that.

you can deselect that,but make sure you have at least one export table parameter.

Mapping the read operation to table parameter might give you an issue .

you can have two entities in the same service,one for Invoice header and one for line items and

create association between these entities.navigation  can be used to fetch the line items for header.

and map the query operation of line item entity to RFC that returns this line items.

delegated key error:

  are you inheriting an entity  to create an entity??

Best Regards,

   Goutham