cancel
Showing results for 
Search instead for 
Did you mean: 

Cross-border STO out of Brazil

hans_thyssen
Explorer
0 Kudos

Hi team,

we have a production site in Brazil and wants to transfer goods via a STO to our plant in Argentina.

Until now I don't succeed to finish this flow.

When I use the setup SAP recommends (using UB order and MoT 862) no Nota Fiscal is generated.  The button is available in the material document but there is no NF (message 8B262 - Material document is not linked to a Nota Fiscal - is displayed).

When I use the setup we are using in Europe (via intercompany STO => no item category U and movement type 643) and add extra customising for Brazil for MoT 643, we get a lot of errors during NF generation.  1st error no partner determined.

Did someone use STO's in Brazil for cross-border (and cross-company) transfers?

Thanks a lot,

Hans

Accepted Solutions (1)

Accepted Solutions (1)

leandropia
Contributor
0 Kudos

Hans,

The STO via 861/862 was designed to transfer goods between plants that belongs to a same company code (between Brazilian Plants/Business Places);

To transfer goods from Brazil to Argentina, although from a business perspective it is a STO, to the localization design (and also legal requirements point of view) this is a customer and vendor operation.

You should not use these movement types for that (861/862).

PO > Delivery > Billing Document?

You don't assign NF Category Derivation to Movement type for Intercompany STO.

Check your settings at: SM30 > J_1BSDICA and J_1BTVAKV and J_1BSDIC

Leandro da Pia Nascimento

hans_thyssen
Explorer
0 Kudos

Hi Leandro,

do you want to say that you can not use a stock transport order for cross-border deliveries (receiving plant = outside BR)?

I did setup the tables you are indicating for dummy sales order type ZDL (which is SAP using in case of STO's).  I tried it with MoT 862 and 643.

And did set it up for BR as a stock transfer (2) and standard item (1).

So I guess it is not possible?  That would be a pitty because for planning reasons (link w/ APO), STO's are preferred.

Thanks a lot for your quick answer.

Hans

leandropia
Contributor
0 Kudos

No, that's what I am not saying... I'm sorry if I was not clear.

You can use STO, so, let the planning people know to calm down .

The STO OSS Notes 199233 and 888805 it explains the process to use the STO to transfer goods between 2 plants that belongs to the same company code and they are located in Brazil (Internal transport order / Intracompany).

To the STO Intercompany (Cross-Borders) you can't use 861/862 movement types.

You can use this OSS Note as a guide, but you have to understand that the movement types above can't be used.

You said that when you assigned the Movement 643 you got the message "no partner determined" right?

Send a screenshot of Nota Fiscal Item Type 2 (Stock Transfer) from tables: J_1BITEMTYPES and J_1BNFITMRULEV;

If J_1BNFITMRULEV is missing it, then go to SE38 and run the report J_1BFILLRECTYPES

Thanks

Leandro da Pia Nascimento

hans_thyssen
Explorer
0 Kudos

Hi Leandro,

since table J_1BITEMTYPES does only contain the text linked to 2 I did not add a screen print.

The definition of type 2, you can find in the attachment.

When posting GI we get indeed error 8B 146 "Enter a partner type, .....".

There is a place where you can add your own code but when we fill it via debug, we get the next error 8B 147 (Enter currency in the document).

We don't know how many errors will follow so we hope there is a standard solution .

Thanks,

Hans

hans_thyssen
Explorer
0 Kudos

One extra question because I am still confused.

Do we need to use NF item type 2 (stock transfer) or should we use 1 (standard item) which is used for sale?  In your 1st reply, you mentioned that cross-border must be seen as a sale i.o. a stock transfer.

Thanks, Hans

leandropia
Contributor
0 Kudos

You are going to use 2 - Stock Transfer Item;

What is the NF Type on J_1BTVAKV?

hans_thyssen
Explorer
0 Kudos

Well ... that is a difficult one.  We have intracompany STO's (between 2 plants in BR of the same comp. code) and that is working w/ MoT 641.

And we have the cross-company STO.

In table J_1BTVAK, you link the NF type to a sales order type.  For STO's the determined SO type is the dummy ZDL (since there is no preceding SO).  It is the same for both types of STO.

Currently NF type ZH is linked to it (for the intracompany STO) but I changed it already to ZI (which is the one setup for cross-company). It didn't solve my issue.

Attached you find the definition of both NF types.

leandropia
Contributor
0 Kudos

On ZH, try to leave the Invoice verification box (partner data) in blank to all 3 fields

Former Member
0 Kudos

Hi Hans, please check the bp documents.

SAP Best Practices Baseline Package

Technical Information -> Content Library -> 141 - INTERNAL PROCUREMENT CROSS-COMPANY STOCK TRANSFER

May it can help you to implement this process. You have to check how to adequate it to brazil-argentina.

Best regards

Eduardo Chagas

Answers (2)

Answers (2)

hans_thyssen
Explorer
0 Kudos

Thanks to Leandro I did succeed to setup the cross-border STO.

Do not use the UB document type nor the Brazilian MoT's(8...). They are not working.

You have to use the intercompany STO as you should normally do (which is a copy of an NB).

Also use the standard MoT in this flow (which is normally 643).

Take care not to link any NF settings to this MoT because this will result in errors.

All other NF settings should be setup. On sales doc type (dummy doc type because STO) and on billing type.

When this is done, you will be able to post goods issue your delivery and no NF is created.

The NF will be created at the moment of the intercompany billing.

Good luck.

JL23
Active Contributor
0 Kudos

There is an extra forum dealing with Nota Fiscal

but it is in Portuguese language.

hans_thyssen
Explorer
0 Kudos

Hi Jürgen,  thanks.

I asked my Brazilian colleague to check that NF forum but unfortunately, no info related to my question.

Still looking if cross-border (cross-company) is possible in Brazil.

You can use PO-SO flow but SAP recommends to use STO's between SAP plants.
Hans