Quantcast
Channel: SCN: Message List - SPED output type issue
Viewing all 18 articles
Browse latest View live

SPED output type issue

$
0
0

Hi All,

 

We have are trying to set-up the standard function to copy the outbound delivery for STO into an inbound delivery by using the SPED output type.

 

Issue description:

We have performed all the config for the SPED output set-up as per OSS notes 965176 and 1119073

The access sequences and output determination procedures are set and the requirement type 408 is assigned to the determination procedure as per OSS notes.

 

We have performed the set-up in VV21/VV22 for the SPED output type and assigned this to the delivery type NLCC.

Upon PGI of the outbound delivery the SPED output is not being triggered. Checking the output determination process in the outbound delivery returns for SPED message 502 output requirement 408 not fulfilled.

 

After analysis of the code I found out that the following piece of coding in the LV61B408 include (coding behind the requirement type 408) is making that the SPED is not being determined and the 502 error message being returned in the output determination analysis.

 

6-06-2013 19-50-20.png

 

If in debug mode I put the plant value in the KOMKBV2-WERKS field the output is being triggered.

 

Question to the experts:

Can someone tell me how the WERKS (receiving plant code) is filled into the KOMKBV2-WERKS field for the outbound delivery?

I have searched OSS and looked at the different notes that are there and also searched via google and on the SCN website but could not find any information in this regard.

 

Testing already performed:

I created a condition table for the access sequence that contains the delivery type and also the KOMKBV2-WERKS field and then set-up the output condition SPED using both the delivery type and the plant code.

This did not have any effect to get the SPED condition determined. The debugging also showed that the KOMKBV2-WERKS field was not filled.

 

I checked the material master data, vendor master data, customer master data and scheduling agreement and don't see anything wrong.

Adding the SPED condition manually to the outbound delivery everything is working correctly and the inbound delivery is being created based on the outbound delivery data.

 

Thanks in advance for the responses,


SPED output type issue

$
0
0

I think the receiving plant should be taken from LIKP-WERKS field.

check with SE16 the content of that field and see as well its F1 field docu.

Re: SPED output type issue

$
0
0

Hi Jürgen,

 

The LIKP-WERKS is indeed blank.

According to the help documentation the following information is provided.

 

Receiving plant for deliveries

Receiving plant (for customer number) for a delivery.

How this field is filled and interpreted depends on the document category/delivery type. You can distinguish between the following cases:

 

  • Delivery from stock transport order
    Recipient of the delivery/ordering plant from the stock transport
    order
  • Shipping notification
    The shipping notification may refer to several recipients. In this
    case, the field is empty.
  • Rough goods receipt
    Plant for which you create the rough goods issue.

For the remaining deliveries, the field contains the customer's plant number, provided that this customer has been maintained.

 

In our case we are doing cross company stock transports using the document type NLCC but here the plant code for the receiving plant is not flowing into the delivery and is thus also not present in LIKP.

 

As far as I can find all the definitions are done and normal SAP to SAP cross company purchasing is working with only the outbound delivery but the conversion from the outbound to the inbound is not working as the receiving plant field in LIKP is not being filled.

 

Any Idea on how what could be missing to fill the field in LIKP?

Re: SPED output type issue

$
0
0

Dear Peter,

 

Yes,  LIKP-WERKS not fill is the reason of the problem for auto SPED.

 

If you have Retail system, that plant is derived from the plant a customer is
assigned to via customizing in table T001W.

If you don't use Retail, it is impossible to fill LIKP-WERKS.


Field LIKP-WERKS is only filled for outbound replenishment deliveries (delivery type NL, NLCC) that are created from stock transfer orders via transaction VL10* or VL04. It is filled there with the receiving
plant of the STO.

 

Regards,

ian Wong Loke Foong

Re: SPED output type issue

$
0
0

I think you just missed to assign the supplying plant to a vendor master in XK02 purchasing data view from menu Extras > additional data purchasing.

Re: SPED output type issue

$
0
0

Hi Jürgen,

 

No this is assigned I checked. Also If this would not be assigned then when I create the scheduling agreement or the PO the supplying plant box would not be showing up.

 

7-06-2013 9-37-50.png

 

Below is a screenshot shows that the supplying plant is copied into the scheduling agreement.

7-06-2013 9-41-21.png

Re: SPED output type issue

$
0
0

Hi Ian,

 

I'm not fully getting your response, initially you are saying that the LIKP-WERKS field is only filled if we are using retail which we are not.

Then in the next section you say that the LIKP-WERKS is only filled for replenishment deliveries of type NL or NLCC and if the outbound is created via the VL10* or VL04 transactions.

 

We are using NLCC delivery type and we are creating the outbound delivery via the VL10* transactions.

 

So what do I now need to conclude that it's only working in retail or that it's working in the standard system if using NLCC + VL10* ?

 

By the way none of the SAP notes regarding the SPED message are referring that this function is only working in retail.

Re: SPED output type issue

$
0
0

Hello Peter,

 

What is the item category (Inbound delivery) you are using? check in 0VLP.

inbound delivery will use another del. item category i used ELST in my process set up.

 

Have you defined the item category determination for the same in 0184 transaction.

EL  NORM V ELST ELST,

Regards

Nisha


Re: SPED output type issue

$
0
0

Hi Nisha,

 

We are using the standard EL delivery type and ELN item category.

 

The item category determination is also defined in the system EL NORM V     ELN

I also tried with EL NORM V ELN ELN but that didn't make a difference.

 

Regards,

Peter

Re: SPED output type issue

$
0
0

Dear Peter,

 

Please ignore explanation for retails system. Actually i am explaining the same for retail system that only

NL and NLCC will works but not others for retail. So if you do not have retail, then of course NLCC will works.

 

After analysis, i found this field normally coming from LIKP table, if no receiving plant is contained so the

requirement will not be fulfilled and the output type will not be issued.

 

Regards,

ian Wong Loke Foong

Re: SPED output type issue

$
0
0

Dear Peter,

 

After analysis, i found this field normally coming from LIKP table, if no receiving plant is contained so the

requirement will not be fulfilled and the output type will not be issued. can you please check table if

your LIKP contain receiving plants but this had been answered by Jurgen. If Jurgen replied not help,

then you may also check if you have own condition table with plant(s), storage location and movement type.

Please check user exit USEREXIT_KOMKBV2_FILL in include RVCOMFZZ.

 

Regards,

ian Wong Loke Foong

Re: SPED output type issue

$
0
0

Hi Ian,

 

Jürgen already informed earlier to check the LIKP-WERKS for the delivery and this field is blank in LIKP. The thing that is not clear is why is this blank for the stock transport delivery.

 

I have checked already all the settings and as you can read in my responses to Jürgen and Nisha all the data that I can think of for cross company stock transport is defined.

 

The stock transport process is also working correctly the only thing that is not working is to get the SPED output type triggered.

 

I checked the T001W table and there all is assigned, plant, valuation area, customer and vendor number and the sales org

Re: SPED output type issue

$
0
0

Hi Peter,

 

Check ship-to-party is assigned to your defined customer account group.

 

Customer should assigned to sales area aslo.

 

 

Regards

Sanjeet Kumar

Re: SPED output type issue

$
0
0

Hi Sanjeet,

 

The ship to party is assigned and the customer is assigned to the sales org.

 

Regards,

Re: SPED output type issue

$
0
0

Hi Peter,

 

Did you configure assign the shipping point as receiving point?

 

regards

Satya


Re: SPED output type issue

$
0
0

Hi Polina,

 

Yes the shipping point as receiving point has been assigned and tested but no luck.

Re: SPED output type issue

$
0
0

Update:

 

After some searching and debugging I found out why the LIKP-WEKRS field is not being filled.

The issue comes from a copy control that is defined for the header.

 

The config for this copy control can be found in SPRO under Logistics execution >> Shipping >> Copying control >> Specify copy control for deliveries

 

There for the NLCC delivery type we have a custom copy control that was implemented before I joined the SAP team.

Copy control header 1.png

 

Copy control header 2.png

 

After making this change the LIKP-WERKS field is being populated however the SPED output is still not being triggered.

I will continue to check this further and if I find the solution I will post the result here.

 

Of course if someone still has an idea, don't hesitate to provide your info.

Re: SPED output type issue

$
0
0

Final update:

The issue is resolved the last step that I was missing was a stupid setting that I overlooked each time I looked at the output determination procedure for the SPED output. The manual only indicator was active.

 

So we have done a change to our custom copy control routine to fill up the LIKP-WERKS and removed the manual only indicator, now the SPED output is triggered and the inbound is created.

 

Thanks to all for your suggestions and time spend.

 

Jürgen L, if you see this how to I mark this subject as answered?

Viewing all 18 articles
Browse latest View live